Scheduling wireless communications

ABSTRACT

Control information may be used to schedule communications between a wireless device and a base station. The wireless device may monitor control channels associated with one or more cells to receive the control information.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.17/186,572, filed on Feb. 26, 2021, which claims the benefit of U.S.Provisional Application Nos. 62/982,846, 62/982,849, and 62/982,909,each of which was filed on Feb. 28, 2020. Each of the above-referencedapplications is hereby incorporated by reference in its entirety.

BACKGROUND

A base station sends control signals to schedule downlink/uplinktransmissions. A wireless device sends/receives information based on thecontrol signals.

SUMMARY

The following summary presents a simplified summary of certain features.The summary is not an extensive overview and is not intended to identifykey or critical elements.

Control information may be used for scheduling wireless communications.The control information may be sent via resources (e.g., using searchspaces) associated with self-carrier scheduling or via resourcesassociated with cross-carrier scheduling. A wireless device may monitorspecific search spaces associated with one or more cells (e.g., forself-carrier scheduling and/or for cross-carrier scheduling) to receivedifferent types of control information. A base station may explicitly orimplicitly indicate whether a search space and/or any other wirelessresource (e.g., a bandwidth part (BWP)) of a cell is configured forcross-carrier scheduling or self-carrier scheduling. A base station maydynamically activate or deactivate cross-carrier scheduling (e.g., viacontrol signaling). Search space monitoring and carrier scheduling, asdescribed herein, may facilitate improved reliability facilitated byself-carrier scheduling and/or improved control signaling throughputfacilitated by cross-carrier scheduling.

These and other features and advantages are described in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

Some features are shown by way of example, and not by limitation, in theaccompanying drawings. In the drawings, like numerals reference similarelements.

FIG. 1A and FIG. 1B show example communication networks.

FIG. 2A shows an example user plane.

FIG. 2B shows an example control plane configuration.

FIG. 3 shows example of protocol layers.

FIG. 4A shows an example downlink data flow for a user planeconfiguration.

FIG. 4B shows an example format of a Medium Access Control (MAC)subheader in a MAC Protocol Data Unit (PDU).

FIG. 5A shows an example mapping for downlink channels.

FIG. 5B shows an example mapping for uplink channels.

FIG. 6 shows example radio resource control (RRC) states and RRC statetransitions.

FIG. 7 shows an example configuration of a frame.

FIG. 8 shows an example resource configuration of one or more carriers.

FIG. 9 shows an example configuration of bandwidth parts (BWPs).

FIG. 10A shows example carrier aggregation configurations based oncomponent carriers.

FIG. 10B shows example group of cells.

FIG. 11A shows an example mapping of one or more synchronizationsignal/physical broadcast channel (SS/PBCH) blocks.

FIG. 11B shows an example mapping of one or more channel stateinformation reference signals (CSI-RSs).

FIG. 12A shows examples of downlink beam management procedures.

FIG. 12B shows examples of uplink beam management procedures.

FIG. 13A shows an example four-step random access procedure.

FIG. 13B shows an example two-step random access procedure.

FIG. 13C shows an example two-step random access procedure.

FIG. 14A shows an example of control resource set (CORESET)configurations.

FIG. 14B shows an example of a control channel element to resourceelement group (CCE-to-REG) mapping.

FIG. 15A shows an example of communications between a wireless deviceand a base station.

FIG. 15B shows example elements of a computing device that may be usedto implement any of the various devices described herein.

FIG. 16A, FIG. 16B, FIG. 16C, and FIG. 16D show examples of uplink anddownlink signal transmission.

FIG. 17A and FIG. 17B show example secondary cell (SCell)activation/deactivation MAC control element (CE) formats.

FIG. 18A shows an example of an SCell hibernation MAC CE format.

FIG. 18B shows an example of an SCell hibernation MAC CE format.

FIG. 18C shows example MAC CEs for SCell state transitions.

FIG. 19 shows example downlink control information (DCI) formats.

FIG. 20 shows example BWP management on an SCell.

FIG. 21A shows an example random access procedure.

FIG. 21B shows an example method for a random access procedure.

FIG. 21C shows an example method for a random access procedure.

FIG. 21D shows an example method for a random access procedure.

FIG. 21E shows an example method for a random access procedure.

FIG. 22A shows an example of switching from self-carrier scheduling andcross-carrier scheduling.

FIG. 22B shows an example method for signal transmission.

FIG. 22C shows an example method for signal reception.

FIG. 22D shows an example method for signal transmission.

FIG. 22E shows an example method for signal reception.

FIG. 23A shows an example of switching from cross-carrier scheduling andself-carrier scheduling.

FIG. 23B shows an example method for signal transmission.

FIG. 23C shows an example method for signal reception.

FIG. 23D shows an example method for signal transmission.

FIG. 23E shows an example method for signal reception.

FIG. 24A and FIG. 24B show example methods for switching betweencross-carrier scheduling and self-carrier scheduling.

FIG. 25A shows an example method for monitoring search spaces.

FIG. 25B shows an example method for monitoring search spaces.

FIG. 26A shows an example of switching between self-carrier schedulingand cross-carrier scheduling.

FIG. 26B shows an example method for signal transmission.

FIG. 26C shows an example method for signal reception.

FIG. 26D shows an example method for signal transmission.

FIG. 26E shows an example method for signal reception.

FIG. 27 shows an example configuration of a BWP.

FIG. 28A shows an example configuration of a plurality of BWP sets for acell.

FIG. 28B shows an example method for signal transmission.

FIG. 28C shows an example method for signal reception.

FIG. 28D shows an example method for signal transmission.

FIG. 28E shows an example method for signal reception.

FIG. 29 shows an example configuration of a plurality of BWP sets for acell.

FIG. 30 shows an example search space configuration of a search space.

FIG. 31A shows an example configuration of search spaces.

FIG. 31B shows an example method for signal transmission.

FIG. 31C shows an example method for signal reception.

FIG. 31D shows an example method for signal transmission.

FIG. 31E shows an example method for signal reception.

FIG. 32 shows an example configuration of search spaces.

FIG. 33 shows an example configuration of search spaces.

FIG. 34A shows an example method for self-carrier scheduling andcross-carrier scheduling based on configuration of BWP sets.

FIG. 34B shows an example method for self-carrier scheduling andcross-carrier scheduling.

FIG. 35A and FIG. 35B shows an example method of self-carrier schedulingand cross-carrier scheduling based on configuration of search spaces.

FIG. 36 shows an example method for determining a scheduling type for aDL BWP.

FIG. 37A shows example communication based on cross-carrier schedulingand self-carrier scheduling.

FIG. 37B shows an example method for signal transmission.

FIG. 37C shows an example method for signal reception.

FIG. 37D shows an example method for signal transmission.

FIG. 37E shows an example method for signal reception.

FIG. 38A shows example communication based on a slot format indication.

FIG. 38B shows an example method for signal transmission.

FIG. 38C shows an example method for signal reception.

FIG. 38D shows an example method for signal transmission.

FIG. 38E shows an example method for signal reception.

FIG. 39A shows example communication based on cross-carrier schedulingand self-carrier scheduling.

FIG. 39B shows an example method for signal transmission.

FIG. 39C shows an example method for signal reception.

FIG. 39D shows an example method for signal transmission.

FIG. 39E shows an example method for signal reception.

FIG. 40 shows an example cross-carrier scheduling configuration.

FIG. 41A and FIG. 41B show example MAC CE formats.

FIG. 42A and FIG. 42B show example MAC CE formats.

FIG. 43A and FIG. 43B shows example methods for monitoring search spacesbased on traffic indicators.

FIG. 44A and FIG. 44B shows example methods for monitoring search spacesbased on a slot format indication.

DETAILED DESCRIPTION

The accompanying drawings and descriptions provide examples. It is to beunderstood that the examples shown in the drawings and/or described arenon-exclusive, and that features shown and described may be practiced inother examples. Examples are provided for operation of wirelesscommunication systems, which may be used in the technical field ofmulticarrier communication systems. More particularly, the technologydisclosed herein may relate to scheduling for wireless communications,such as self-carrier, cross-carrier scheduling, and the like.

FIG. 1A shows an example communication network 100. The communicationnetwork 100 may comprise a mobile communication network). Thecommunication network 100 may comprise, for example, a public landmobile network (PLMN) operated/managed/run by a network operator. Thecommunication network 100 may comprise one or more of a core network(CN) 102, a radio access network (RAN) 104, and/or a wireless device106. The communication network 100 may comprise, and/or a device withinthe communication network 100 may communicate with (e.g., via CN 102),one or more data networks (DN(s)) 108. The wireless device 106 maycommunicate with one or more DNs 108, such as public DNs (e.g., theInternet), private DNs, and/or intra-operator DNs. The wireless device106 may communicate with the one or more DNs 108 via the RAN 104 and/orvia the CN 102. The CN 102 may provide/configure the wireless device 106with one or more interfaces to the one or more DNs 108. As part of theinterface functionality, the CN 102 may set up end-to-end connectionsbetween the wireless device 106 and the one or more DNs 108,authenticate the wireless device 106, provide/configure chargingfunctionality, etc.

The wireless device 106 may communicate with the RAN 104 via radiocommunications over an air interface. The RAN 104 may communicate withthe CN 102 via various communications (e.g., wired communications and/orwireless communications). The wireless device 106 may establish aconnection with the CN 102 via the RAN 104. The RAN 104 mayprovide/configure scheduling, radio resource management, and/orretransmission protocols, for example, as part of the radiocommunications. The communication direction from the RAN 104 to thewireless device 106 over/via the air interface may be referred to as thedownlink and/or downlink communication direction. The communicationdirection from the wireless device 106 to the RAN 104 over/via the airinterface may be referred to as the uplink and/or uplink communicationdirection. Downlink transmissions may be separated and/or distinguishedfrom uplink transmissions, for example, based on at least one of:frequency division duplexing (FDD), time-division duplexing (TDD), anyother duplexing schemes, and/or one or more combinations thereof.

As used throughout, the term “wireless device” may comprise one or moreof: a mobile device, a fixed (e.g., non-mobile) device for whichwireless communication is configured or usable, a computing device, anode, a device capable of wirelessly communicating, or any other devicecapable of sending and/or receiving signals. As non-limiting examples, awireless device may comprise, for example: a telephone, a cellularphone, a Wi-Fi phone, a smartphone, a tablet, a computer, a laptop, asensor, a meter, a wearable device, an Internet of Things (IoT) device,a hotspot, a cellular repeater, a vehicle road side unit (RSU), a relaynode, an automobile, a wireless user device (e.g., user equipment (UE),a user terminal (UT), etc.), an access terminal (AT), a mobile station,a handset, a wireless transmit and receive unit (WTRU), a wirelesscommunication device, and/or any combination thereof.

The RAN 104 may comprise one or more base stations (not shown). As usedthroughout, the term “base station” may comprise one or more of: a basestation, a node, a Node B (NB), an evolved NodeB (eNB), a gNB, anng-eNB, a relay node (e.g., an integrated access and backhaul (JAB)node), a donor node (e.g., a donor eNB, a donor gNB, etc.), an accesspoint (e.g., a Wi-Fi access point), a transmission and reception point(TRP), a computing device, a device capable of wirelessly communicating,or any other device capable of sending and/or receiving signals. A basestation may comprise one or more of each element listed above. Forexample, a base station may comprise one or more TRPs. As othernon-limiting examples, a base station may comprise for example, one ormore of: a Node B (e.g., associated with Universal MobileTelecommunications System (UMTS) and/or third-generation (3G)standards), an Evolved Node B (eNB) (e.g., associated withEvolved-Universal Terrestrial Radio Access (E-UTRA) and/orfourth-generation (4G) standards), a remote radio head (RRH), a basebandprocessing unit coupled to one or more remote radio heads (RRHs), arepeater node or relay node used to extend the coverage area of a donornode, a Next Generation Evolved Node B (ng-eNB), a Generation Node B(gNB) (e.g., associated with NR and/or fifth-generation (5G) standards),an access point (AP) (e.g., associated with, for example, Wi-Fi or anyother suitable wireless communication standard), any other generationbase station, and/or any combination thereof. A base station maycomprise one or more devices, such as at least one base station centraldevice (e.g., a gNB Central Unit (gNB-CU)) and at least one base stationdistributed device (e.g., a gNB Distributed Unit (gNB-DU)).

A base station (e.g., in the RAN 104) may comprise one or more sets ofantennas for communicating with the wireless device 106 wirelessly(e.g., via an over the air interface). One or more base stations maycomprise sets (e.g., three sets or any other quantity of sets) ofantennas to respectively control multiple cells or sectors (e.g., threecells, three sectors, any other quantity of cells, or any other quantityof sectors). The size of a cell may be determined by a range at which areceiver (e.g., a base station receiver) may successfully receivetransmissions from a transmitter (e.g., a wireless device transmitter)operating in the cell. One or more cells of base stations (e.g., byalone or in combination with other cells) may provide/configure a radiocoverage to the wireless device 106 over a wide geographic area tosupport wireless device mobility. A base station comprising threesectors (e.g., or n-sector, where n refers to any quantity n) may bereferred to as a three-sector site (e.g., or an n-sector site) or athree-sector base station (e.g., an n-sector base station).

One or more base stations (e.g., in the RAN 104) may be implemented as asectored site with more or less than three sectors. One or more basestations of the RAN 104 may be implemented as an access point, as abaseband processing device/unit coupled to several RRHs, and/or as arepeater or relay node used to extend the coverage area of a node (e.g.,a donor node). A baseband processing device/unit coupled to RRHs may bepart of a centralized or cloud RAN architecture, for example, where thebaseband processing device/unit may be centralized in a pool of basebandprocessing devices/units or virtualized. A repeater node may amplify andsend (e.g., transmit, retransmit, rebroadcast, etc.) a radio signalreceived from a donor node. A relay node may perform the substantiallythe same/similar functions as a repeater node. The relay node may decodethe radio signal received from the donor node, for example, to removenoise before amplifying and sending the radio signal.

The RAN 104 may be deployed as a homogenous network of base stations(e.g., macrocell base stations) that have similar antenna patternsand/or similar high-level transmit powers. The RAN 104 may be deployedas a heterogeneous network of base stations (e.g., different basestations that have different antenna patterns). In heterogeneousnetworks, small cell base stations may be used to provide/configuresmall coverage areas, for example, coverage areas that overlap withcomparatively larger coverage areas provided/configured by other basestations (e.g., macrocell base stations). The small coverage areas maybe provided/configured in areas with high data traffic (or so-called“hotspots”) or in areas with a weak macrocell coverage. Examples ofsmall cell base stations may comprise, in order of decreasing coveragearea, microcell base stations, picocell base stations, and femtocellbase stations or home base stations.

Examples described herein may be used in a variety of types ofcommunications. For example, communications may be in accordance withthe Third-Generation Partnership Project (3GPP) (e.g., one or morenetwork elements similar to those of the communication network 100),communications in accordance with Institute of Electrical andElectronics Engineers (IEEE), communications in accordance withInternational Telecommunication Union (ITU), communications inaccordance with International Organization for Standardization (ISO),etc. The 3GPP has produced specifications for multiple generations ofmobile networks: a 3G network known as UMTS, a 4G network known asLong-Term Evolution (LTE) and LTE Advanced (LTE-A), and a 5G networkknown as 5G System (5GS) and NR system. 3GPP may produce specificationsfor additional generations of communication networks (e.g., 6G and/orany other generation of communication network). Examples may bedescribed with reference to one or more elements (e.g., the RAN) of a3GPP 5G network, referred to as a next-generation RAN (NG-RAN), or anyother communication network, such as a 3GPP network and/or a non-3GPPnetwork. Examples described herein may be applicable to othercommunication networks, such as 3G and/or 4G networks, and communicationnetworks that may not yet be finalized/specified (e.g., a 3GPP 6Gnetwork), satellite communication networks, and/or any othercommunication network. NG-RAN implements and updates 5G radio accesstechnology referred to as NR and may be provisioned to implement 4Gradio access technology and/or other radio access technologies, such asother 3GPP and/or non-3GPP radio access technologies.

FIG. 1B shows an example communication network 150. The communicationnetwork may comprise a mobile communication network. The communicationnetwork 150 may comprise, for example, a PLMN operated/managed/run by anetwork operator. The communication network 150 may comprise one or moreof: a CN 152 (e.g., a 5G core network (5G-CN)), a RAN 154 (e.g., anNG-RAN), and/or wireless devices 156A and 156B (collectively wirelessdevice(s) 156). The communication network 150 may comprise, and/or adevice within the communication network 150 may communicate with (e.g.,via CN 152), one or more data networks (DN(s)) 170. These components maybe implemented and operate in substantially the same or similar manneras corresponding components described with respect to FIG. 1A.

The CN 152 (e.g., 5G-CN) may provide/configure the wireless device(s)156 with one or more interfaces to one or more DNs 170, such as publicDNs (e.g., the Internet), private DNs, and/or intra-operator DNs. Aspart of the interface functionality, the CN 152 (e.g., 5G-CN) may set upend-to-end connections between the wireless device(s) 156 and the one ormore DNs, authenticate the wireless device(s) 156, and/orprovide/configure charging functionality. The CN 152 (e.g., the 5G-CN)may be a service-based architecture, which may differ from other CNs(e.g., such as a 3GPP 4G CN). The architecture of nodes of the CN 152(e.g., 5G-CN) may be defined as network functions that offer servicesvia interfaces to other network functions. The network functions of theCN 152 (e.g., 5G CN) may be implemented in several ways, for example, asnetwork elements on dedicated or shared hardware, as software instancesrunning on dedicated or shared hardware, and/or as virtualized functionsinstantiated on a platform (e.g., a cloud-based platform).

The CN 152 (e.g., 5G-CN) may comprise an Access and Mobility ManagementFunction (AMF) device 158A and/or a User Plane Function (UPF) device158B, which may be separate components or one component AMF/UPF device158. The UPF device 158B may serve as a gateway between a RAN 154 (e.g.,NG-RAN) and the one or more DNs 170. The UPF device 158B may performfunctions, such as: packet routing and forwarding, packet inspection anduser plane policy rule enforcement, traffic usage reporting, uplinkclassification to support routing of traffic flows to the one or moreDNs 170, quality of service (QoS) handling for the user plane (e.g.,packet filtering, gating, uplink/downlink rate enforcement, and uplinktraffic verification), downlink packet buffering, and/or downlink datanotification triggering. The UPF device 158B may serve as an anchorpoint for intra-/inter-Radio Access Technology (RAT) mobility, anexternal protocol (or packet) data unit (PDU) session point ofinterconnect to the one or more DNs, and/or a branching point to supporta multi-homed PDU session. The wireless device(s) 156 may be configuredto receive services via a PDU session, which may be a logical connectionbetween a wireless device and a DN.

The AMF device 158A may perform functions, such as: Non-Access Stratum(NAS) signaling termination, NAS signaling security, Access Stratum (AS)security control, inter-CN node signaling for mobility between accessnetworks (e.g., 3GPP access networks and/or non-3GPP networks), idlemode wireless device reachability (e.g., idle mode UE reachability forcontrol and execution of paging retransmission), registration areamanagement, intra-system and inter-system mobility support, accessauthentication, access authorization including checking of roamingrights, mobility management control (e.g., subscription and policies),network slicing support, and/or session management function (SMF)selection. NAS may refer to the functionality operating between a CN anda wireless device, and AS may refer to the functionality operatingbetween a wireless device and a RAN.

The CN 152 (e.g., 5G-CN) may comprise one or more additional networkfunctions that may not be shown in FIG. 1B. The CN 152 (e.g., 5G-CN) maycomprise one or more devices implementing at least one of: a SessionManagement Function (SMF), an NR Repository Function (NRF), a PolicyControl Function (PCF), a Network Exposure Function (NEF), a UnifiedData Management (UDM), an Application Function (AF), an AuthenticationServer Function (AUSF), and/or any other function.

The RAN 154 (e.g., NG-RAN) may communicate with the wireless device(s)156 via radio communications (e.g., an over the air interface). Thewireless device(s) 156 may communicate with the CN 152 via the RAN 154.The RAN 154 (e.g., NG-RAN) may comprise one or more first-type basestations (e.g., gNBs comprising a gNB 160A and a gNB 160B (collectivelygNBs 160)) and/or one or more second-type base stations (e.g., ng eNBscomprising an ng-eNB 162A and an ng-eNB 162B (collectively ng eNBs162)). The RAN 154 may comprise one or more of any quantity of types ofbase station. The gNBs 160 and ng eNBs 162 may be referred to as basestations. The base stations (e.g., the gNBs 160 and ng eNBs 162) maycomprise one or more sets of antennas for communicating with thewireless device(s) 156 wirelessly (e.g., an over an air interface). Oneor more base stations (e.g., the gNBs 160 and/or the ng eNBs 162) maycomprise multiple sets of antennas to respectively control multiplecells (or sectors). The cells of the base stations (e.g., the gNBs 160and the ng-eNBs 162) may provide a radio coverage to the wirelessdevice(s) 156 over a wide geographic area to support wireless devicemobility.

The base stations (e.g., the gNBs 160 and/or the ng-eNBs 162) may beconnected to the CN 152 (e.g., 5G CN) via a first interface (e.g., an NGinterface) and to other base stations via a second interface (e.g., anXn interface). The NG and Xn interfaces may be established using directphysical connections and/or indirect connections over an underlyingtransport network, such as an internet protocol (IP) transport network.The base stations (e.g., the gNBs 160 and/or the ng-eNBs 162) maycommunicate with the wireless device(s) 156 via a third interface (e.g.,a Uu interface). A base station (e.g., the gNB 160A) may communicatewith the wireless device 156A via a Uu interface. The NG, Xn, and Uuinterfaces may be associated with a protocol stack. The protocol stacksassociated with the interfaces may be used by the network elements shownin FIG. 1B to exchange data and signaling messages. The protocol stacksmay comprise two planes: a user plane and a control plane. Any otherquantity of planes may be used (e.g., in a protocol stack). The userplane may handle data of interest to a user. The control plane mayhandle signaling messages of interest to the network elements.

One or more base stations (e.g., the gNBs 160 and/or the ng-eNBs 162)may communicate with one or more AMF/UPF devices, such as the AMF/UPF158, via one or more interfaces (e.g., NG interfaces). A base station(e.g., the gNB 160A) may be in communication with, and/or connected to,the UPF 158B of the AMF/UPF 158 via an NG-User plane (NG-U) interface.The NG-U interface may provide/perform delivery (e.g., non-guaranteeddelivery) of user plane PDUs between a base station (e.g., the gNB 160A)and a UPF device (e.g., the UPF 158B). The base station (e.g., the gNB160A) may be in communication with, and/or connected to, an AMF device(e.g., the AMF 158A) via an NG-Control plane (NG-C) interface. The NG-Cinterface may provide/perform, for example, NG interface management,wireless device context management (e.g., UE context management),wireless device mobility management (e.g., UE mobility management),transport of NAS messages, paging, PDU session management, configurationtransfer, and/or warning message transmission.

A wireless device may access the base station, via an interface (e.g.,Uu interface), for the user plane configuration and the control planeconfiguration. The base stations (e.g., gNBs 160) may provide user planeand control plane protocol terminations towards the wireless device(s)156 via the Uu interface. A base station (e.g., the gNB 160A) mayprovide user plane and control plane protocol terminations toward thewireless device 156A over a Uu interface associated with a firstprotocol stack. A base station (e.g., the ng-eNBs 162) may provideEvolved UMTS Terrestrial Radio Access (E UTRA) user plane and controlplane protocol terminations towards the wireless device(s) 156 via a Uuinterface (e.g., where E UTRA may refer to the 3GPP 4G radio-accesstechnology). A base station (e.g., the ng-eNB 162B) may provide E UTRAuser plane and control plane protocol terminations towards the wirelessdevice 156B via a Uu interface associated with a second protocol stack.The user plane and control plane protocol terminations may comprise, forexample, NR user plane and control plane protocol terminations, 4G userplane and control plane protocol terminations, etc.

The CN 152 (e.g., 5G-CN) may be configured to handle one or more radioaccesses (e.g., NR, 4G, and/or any other radio accesses). It may also bepossible for an NR network/device (or any first network/device) toconnect to a 4G core network/device (or any second network/device) in anon-standalone mode (e.g., non-standalone operation). In anon-standalone mode/operation, a 4G core network may be used to provide(or at least support) control-plane functionality (e.g., initial access,mobility, and/or paging). Although only one AMF/UPF 158 is shown in FIG.1B, one or more base stations (e.g., one or more gNBs and/or one or moreng-eNBs) may be connected to multiple AMF/UPF nodes, for example, toprovide redundancy and/or to load share across the multiple AMF/UPFnodes.

An interface (e.g., Uu, Xn, and/or NG interfaces) between networkelements (e.g., the network elements shown in FIG. 1B) may be associatedwith a protocol stack that the network elements may use to exchange dataand signaling messages. A protocol stack may comprise two planes: a userplane and a control plane. Any other quantity of planes may be used(e.g., in a protocol stack). The user plane may handle data associatedwith a user (e.g., data of interest to a user). The control plane mayhandle data associated with one or more network elements (e.g.,signaling messages of interest to the network elements).

The communication network 100 in FIG. 1A and/or the communicationnetwork 150 in FIG. 1B may comprise any quantity/number and/or type ofdevices, such as, for example, computing devices, wireless devices,mobile devices, handsets, tablets, laptops, internet of things (IoT)devices, hotspots, cellular repeaters, computing devices, and/or, moregenerally, user equipment (e.g., UE). Although one or more of the abovetypes of devices may be referenced herein (e.g., UE, wireless device,computing device, etc.), it should be understood that any device hereinmay comprise any one or more of the above types of devices or similardevices. The communication network, and any other network referencedherein, may comprise an LTE network, a 5G network, a satellite network,and/or any other network for wireless communications (e.g., any 3GPPnetwork and/or any non-3GPP network). Apparatuses, systems, and/ormethods described herein may generally be described as implemented onone or more devices (e.g., wireless device, base station, eNB, gNB,computing device, etc.), in one or more networks, but it will beunderstood that one or more features and steps may be implemented on anydevice and/or in any network.

FIG. 2A shows an example user plane configuration. The user planeconfiguration may comprise, for example, an NR user plane protocolstack. FIG. 2B shows an example control plane configuration. The controlplane configuration may comprise, for example, an NR control planeprotocol stack. One or more of the user plane configuration and/or thecontrol plane configuration may use a Uu interface that may be between awireless device 210 and a base station 220. The protocol stacks shown inFIG. 2A and FIG. 2B may be substantially the same or similar to thoseused for the Uu interface between, for example, the wireless device 156Aand the base station 160A shown in FIG. 1B.

A user plane configuration (e.g., an NR user plane protocol stack) maycomprise multiple layers (e.g., five layers or any other quantity oflayers) implemented in the wireless device 210 and the base station 220(e.g., as shown in FIG. 2A). At the bottom of the protocol stack,physical layers (PHYs) 211 and 221 may provide transport services to thehigher layers of the protocol stack and may correspond to layer 1 of theOpen Systems Interconnection (OSI) model. The protocol layers above PHY211 may comprise a medium access control layer (MAC) 212, a radio linkcontrol layer (RLC) 213, a packet data convergence protocol layer (PDCP)214, and/or a service data application protocol layer (SDAP) 215. Theprotocol layers above PHY 221 may comprise a medium access control layer(MAC) 222, a radio link control layer (RLC) 223, a packet dataconvergence protocol layer (PDCP) 224, and/or a service data applicationprotocol layer (SDAP) 225. One or more of the four protocol layers abovePHY 211 may correspond to layer 2, or the data link layer, of the OSImodel. One or more of the four protocol layers above PHY 221 maycorrespond to layer 2, or the data link layer, of the OSI model.

FIG. 3 shows an example of protocol layers. The protocol layers maycomprise, for example, protocol layers of the NR user plane protocolstack. One or more services may be provided between protocol layers.SDAPs (e.g., SDAPS 215 and 225 shown in FIG. 2A and FIG. 3 ) may performQuality of Service (QoS) flow handling. A wireless device (e.g., thewireless devices 106, 156A, 156B, and 210) may receive servicesthrough/via a PDU session, which may be a logical connection between thewireless device and a DN. The PDU session may have one or more QoS flows310. A UPF (e.g., the UPF 158B) of a CN may map IP packets to the one ormore QoS flows of the PDU session, for example, based on one or more QoSrequirements (e.g., in terms of delay, data rate, error rate, and/or anyother quality/service requirement). The SDAPs 215 and 225 may performmapping/de-mapping between the one or more QoS flows 310 and one or moreradio bearers 320 (e.g., data radio bearers). The mapping/de-mappingbetween the one or more QoS flows 310 and the radio bearers 320 may bedetermined by the SDAP 225 of the base station 220. The SDAP 215 of thewireless device 210 may be informed of the mapping between the QoS flows310 and the radio bearers 320 via reflective mapping and/or controlsignaling received from the base station 220. For reflective mapping,the SDAP 225 of the base station 220 may mark the downlink packets witha QoS flow indicator (QFI), which may bemonitored/detected/identified/indicated/observed by the SDAP 215 of thewireless device 210 to determine the mapping/de-mapping between the oneor more QoS flows 310 and the radio bearers 320.

PDCPs (e.g., the PDCPs 214 and 224 shown in FIG. 2A and FIG. 3 ) mayperform header compression/decompression, for example, to reduce theamount of data that may need to be transmitted over the air interface,ciphering/deciphering to prevent unauthorized decoding of datatransmitted over the air interface, and/or integrity protection (e.g.,to ensure control messages originate from intended sources). The PDCPs214 and 224 may perform retransmissions of undelivered packets,in-sequence delivery and reordering of packets, and/or removal ofpackets received in duplicate due to, for example, a handover (e.g., anintra-gNB handover). The PDCPs 214 and 224 may perform packetduplication, for example, to improve the likelihood of the packet beingreceived. A receiver may receive the packet in duplicate and may removeany duplicate packets. Packet duplication may be useful for certainservices, such as services that require high reliability.

The PDCP layers (e.g., PDCPs 214 and 224) may perform mapping/de-mappingbetween a split radio bearer and RLC channels (e.g., RLC channels 330)(e.g., in a dual connectivity scenario/configuration). Dual connectivitymay refer to a technique that allows a wireless device to communicatewith multiple cells (e.g., two cells) or, more generally, multiple cellgroups comprising: a master cell group (MCG) and a secondary cell group(SCG). A split bearer may be configured and/or used, for example, if asingle radio bearer (e.g., such as one of the radio bearersprovided/configured by the PDCPs 214 and 224 as a service to the SDAPs215 and 225) is handled by cell groups in dual connectivity. The PDCPs214 and 224 may map/de-map between the split radio bearer and RLCchannels 330 belonging to the cell groups.

RLC layers (e.g., RLCs 213 and 223) may perform segmentation,retransmission via Automatic Repeat Request (ARQ), and/or removal ofduplicate data units received from MAC layers (e.g., MACs 212 and 222,respectively). The RLC layers (e.g., RLCs 213 and 223) may supportmultiple transmission modes (e.g., three transmission modes: transparentmode (TM); unacknowledged mode (UM); and acknowledged mode (AM)). TheRLC layers may perform one or more of the noted functions, for example,based on the transmission mode an RLC layer is operating. The RLCconfiguration may be per logical channel. The RLC configuration may notdepend on numerologies and/or Transmission Time Interval (TTI) durations(or other durations). The RLC layers (e.g., RLCs 213 and 223) mayprovide/configure RLC channels as a service to the PDCP layers (e.g.,PDCPs 214 and 224, respectively), such as shown in FIG. 3 .

The MAC layers (e.g., MACs 212 and 222) may performmultiplexing/demultiplexing of logical channels and/or mapping betweenlogical channels and transport channels. The multiplexing/demultiplexingmay comprise multiplexing/demultiplexing of data units/data portions,belonging to the one or more logical channels, into/from TransportBlocks (TBs) delivered to/from the PHY layers (e.g., PHYs 211 and 221,respectively). The MAC layer of a base station (e.g., MAC 222) may beconfigured to perform scheduling, scheduling information reporting,and/or priority handling between wireless devices via dynamicscheduling. Scheduling may be performed by a base station (e.g., thebase station 220 at the MAC 222) for downlink/or and uplink. The MAClayers (e.g., MACs 212 and 222) may be configured to perform errorcorrection(s) via Hybrid Automatic Repeat Request (HARQ) (e.g., one HARQentity per carrier in case of Carrier Aggregation (CA)), priorityhandling between logical channels of the wireless device 210 via logicalchannel prioritization and/or padding. The MAC layers (e.g., MACs 212and 222) may support one or more numerologies and/or transmissiontimings. Mapping restrictions in a logical channel prioritization maycontrol which numerology and/or transmission timing a logical channelmay use. The MAC layers (e.g., the MACs 212 and 222) mayprovide/configure logical channels 340 as a service to the RLC layers(e.g., the RLCs 213 and 223).

The PHY layers (e.g., PHYs 211 and 221) may perform mapping of transportchannels to physical channels and/or digital and analog signalprocessing functions, for example, for sending and/or receivinginformation (e.g., via an over the air interface). The digital and/oranalog signal processing functions may comprise, for example,coding/decoding and/or modulation/demodulation. The PHY layers (e.g.,PHYs 211 and 221) may perform multi-antenna mapping. The PHY layers(e.g., the PHYs 211 and 221) may provide/configure one or more transportchannels (e.g., transport channels 350) as a service to the MAC layers(e.g., the MACs 212 and 222, respectively). Various operations describedherein with reference to communication devices (e.g., base stations, awireless devices, etc.) may be performed by one or more entities in thecommunication device (e.g., a PHY layer entity, a MAC layer entity,and/or one or more other entities corresponding to any other layer inthe communication device).

FIG. 4A shows an example downlink data flow for a user planeconfiguration. The user plane configuration may comprise, for example,the NR user plane protocol stack shown in FIG. 2A. One or more TBs maybe generated, for example, based on a data flow via a user planeprotocol stack. As shown in FIG. 4A, a downlink data flow of three IPpackets (n, n+1, and m) via the NR user plane protocol stack maygenerate two TBs (e.g., at the base station 220). An uplink data flowvia the NR user plane protocol stack may be similar to the downlink dataflow shown in FIG. 4A. The three IP packets (n, n+1, and m) may bedetermined from the two TBs, for example, based on the uplink data flowvia an NR user plane protocol stack. A first quantity of packets (e.g.,three or any other quantity) may be determined from a second quantity ofTBs (e.g., two or another quantity).

The downlink data flow may begin, for example, if the SDAP 225 receivesthe three IP packets (or other quantity of IP packets) from one or moreQoS flows and maps the three packets (or other quantity of packets) toradio bearers (e.g., radio bearers 402 and 404). The SDAP 225 may mapthe IP packets n and n+1 to a first radio bearer 402 and map the IPpacket m to a second radio bearer 404. An SDAP header (labeled with “H”preceding each SDAP SDU shown in FIG. 4A) may be added to an IP packetto generate an SDAP PDU, which may be referred to as a PDCP SDU. Thedata unit transferred from/to a higher protocol layer may be referred toas a service data unit (SDU) of the lower protocol layer, and the dataunit transferred to/from a lower protocol layer may be referred to as aprotocol data unit (PDU) of the higher protocol layer. As shown in FIG.4A, the data unit from the SDAP 225 may be an SDU of lower protocollayer PDCP 224 (e.g., PDCP SDU) and may be a PDU of the SDAP 225 (e.g.,SDAP PDU).

Each protocol layer (e.g., protocol layers shown in FIG. 4A) or at leastsome protocol layers may: perform its own function(s) (e.g., one or morefunctions of each protocol layer described with respect to FIG. 3 ), adda corresponding header, and/or forward a respective output to the nextlower layer (e.g., its respective lower layer). The PDCP 224 may performan IP-header compression and/or ciphering. The PDCP 224 may forward itsoutput (e.g., a PDCP PDU, which is an RLC SDU) to the RLC 223. The RLC223 may optionally perform segmentation (e.g., as shown for IP packet min FIG. 4A). The RLC 223 may forward its outputs (e.g., two RLC PDUs,which are two MAC SDUs, generated by adding respective subheaders to twoSDU segments (SDU Segs)) to the MAC 222. The MAC 222 may multiplex anumber of RLC PDUs (MAC SDUs). The MAC 222 may attach a MAC subheader toan RLC PDU (MAC SDU) to form a TB. The MAC subheaders may be distributedacross the MAC PDU (e.g., in an NR configuration as shown in FIG. 4A).The MAC subheaders may be entirely located at the beginning of a MAC PDU(e.g., in an LTE configuration). The NR MAC PDU structure may reduce aprocessing time and/or associated latency, for example, if the MAC PDUsubheaders are computed before assembling the full MAC PDU.

FIG. 4B shows an example format of a MAC subheader in a MAC PDU. A MACPDU may comprise a MAC subheader (H) and a MAC SDU. Each of one or moreMAC subheaders may comprise an SDU length field for indicating thelength (e.g., in bytes) of the MAC SDU to which the MAC subheadercorresponds; a logical channel identifier (LCID) field foridentifying/indicating the logical channel from which the MAC SDUoriginated to aid in the demultiplexing process; a flag (F) forindicating the size of the SDU length field; and a reserved bit (R)field for future use.

One or more MAC control elements (CEs) may be added to, or insertedinto, the MAC PDU by a MAC layer, such as MAC 223 or MAC 222. As shownin FIG. 4B, two MAC CEs may be inserted/added before two MAC PDUs. TheMAC CEs may be inserted/added at the beginning of a MAC PDU for downlinktransmissions (as shown in FIG. 4B). One or more MAC CEs may beinserted/added at the end of a MAC PDU for uplink transmissions. MAC CEsmay be used for in band control signaling. Example MAC CEs may comprisescheduling-related MAC CEs, such as buffer status reports and powerheadroom reports; activation/deactivation MAC CEs (e.g., MAC CEs foractivation/deactivation of PDCP duplication detection, channel stateinformation (CSI) reporting, sounding reference signal (SRS)transmission, and prior configured components); discontinuous reception(DRX)-related MAC CEs; timing advance MAC CEs; and random access-relatedMAC CEs. A MAC CE may be preceded by a MAC subheader with a similarformat as described for the MAC subheader for MAC SDUs and may beidentified with a reserved value in the LCID field that indicates thetype of control information included in the corresponding MAC CE.

FIG. 5A shows an example mapping for downlink channels. The mapping foruplink channels may comprise mapping between channels (e.g., logicalchannels, transport channels, and physical channels) for downlink. FIG.5B shows an example mapping for uplink channels. The mapping for uplinkchannels may comprise mapping between channels (e.g., logical channels,transport channels, and physical channels) for uplink. Information maybe passed through/via channels between the RLC, the MAC, and the PHYlayers of a protocol stack (e.g., the NR protocol stack). A logicalchannel may be used between the RLC and the MAC layers. The logicalchannel may be classified/indicated as a control channel that may carrycontrol and/or configuration information (e.g., in the NR controlplane), or as a traffic channel that may carry data (e.g., in the NRuser plane). A logical channel may be classified/indicated as adedicated logical channel that may be dedicated to a specific wirelessdevice, and/or as a common logical channel that may be used by more thanone wireless device (e.g., a group of wireless device).

A logical channel may be defined by the type of information it carries.The set of logical channels (e.g., in an NR configuration) may compriseone or more channels described below. A paging control channel (PCCH)may comprise/carry one or more paging messages used to page a wirelessdevice whose location is not known to the network on a cell level. Abroadcast control channel (BCCH) may comprise/carry system informationmessages in the form of a master information block (MIB) and severalsystem information blocks (SIBs). The system information messages may beused by wireless devices to obtain information about how a cell isconfigured and how to operate within the cell. A common control channel(CCCH) may comprise/carry control messages together with random access.A dedicated control channel (DCCH) may comprise/carry control messagesto/from a specific wireless device to configure the wireless device withconfiguration information. A dedicated traffic channel (DTCH) maycomprise/carry user data to/from a specific wireless device.

Transport channels may be used between the MAC and PHY layers. Transportchannels may be defined by how the information they carry issent/transmitted (e.g., via an over the air interface). The set oftransport channels (e.g., that may be defined by an NR configuration orany other configuration) may comprise one or more of the followingchannels. A paging channel (PCH) may comprise/carry paging messages thatoriginated from the PCCH. A broadcast channel (BCH) may comprise/carrythe MIB from the BCCH. A downlink shared channel (DL-SCH) maycomprise/carry downlink data and signaling messages, including the SIBsfrom the BCCH. An uplink shared channel (UL-SCH) may comprise/carryuplink data and signaling messages. A random access channel (RACH) mayprovide a wireless device with an access to the network without anyprior scheduling.

The PHY layer may use physical channels to pass/transfer informationbetween processing levels of the PHY layer. A physical channel may havean associated set of time-frequency resources for carrying theinformation of one or more transport channels. The PHY layer maygenerate control information to support the low-level operation of thePHY layer. The PHY layer may provide/transfer the control information tothe lower levels of the PHY layer via physical control channels (e.g.,referred to as L1/L2 control channels). The set of physical channels andphysical control channels (e.g., that may be defined by an NRconfiguration or any other configuration) may comprise one or more ofthe following channels. A physical broadcast channel (PBCH) maycomprise/carry the MIB from the BCH. A physical downlink shared channel(PDSCH) may comprise/carry downlink data and signaling messages from theDL-SCH, as well as paging messages from the PCH. A physical downlinkcontrol channel (PDCCH) may comprise/carry downlink control information(DCI), which may comprise downlink scheduling commands, uplinkscheduling grants, and uplink power control commands. A physical uplinkshared channel (PUSCH) may comprise/carry uplink data and signalingmessages from the UL-SCH and in some instances uplink controlinformation (UCI) as described below. A physical uplink control channel(PUCCH) may comprise/carry UCI, which may comprise HARQ acknowledgments,channel quality indicators (CQI), pre-coding matrix indicators (PMI),rank indicators (RI), and scheduling requests (SR). A physical randomaccess channel (PRACH) may be used for random access.

The physical layer may generate physical signals to support thelow-level operation of the physical layer, which may be similar to thephysical control channels. As shown in FIG. 5A and FIG. 5B, the physicallayer signals (e.g., that may be defined by an NR configuration or anyother configuration) may comprise primary synchronization signals (PSS),secondary synchronization signals (SSS), channel state informationreference signals (CSI-RS), demodulation reference signals (DM-RS),sounding reference signals (SRS), phase-tracking reference signals (PTRS), and/or any other signals.

One or more of the channels (e.g., logical channels, transport channels,physical channels, etc.) may be used to carry out functions associatedwith the control plan protocol stack (e.g., NR control plane protocolstack). FIG. 2B shows an example control plane configuration (e.g., anNR control plane protocol stack). As shown in FIG. 2B, the control planeconfiguration (e.g., the NR control plane protocol stack) may usesubstantially the same/similar one or more protocol layers (e.g., PHY211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224) asthe example user plane configuration (e.g., the NR user plane protocolstack). Similar four protocol layers may comprise the PHYs 211 and 221,the MACs 212 and 222, the RLCs 213 and 223, and the PDCPs 214 and 224.The control plane configuration (e.g., the NR control plane stack) mayhave radio resource controls (RRCs) 216 and 226 and NAS protocols 217and 237 at the top of the control plane configuration (e.g., the NRcontrol plane protocol stack), for example, instead of having the SDAPs215 and 225. The control plane configuration may comprise an AMF 230comprising the NAS protocol 237.

The NAS protocols 217 and 237 may provide control plane functionalitybetween the wireless device 210 and the AMF 230 (e.g., the AMF 158A orany other AMF) and/or, more generally, between the wireless device 210and a CN (e.g., the CN 152 or any other CN). The NAS protocols 217 and237 may provide control plane functionality between the wireless device210 and the AMF 230 via signaling messages, referred to as NAS messages.There may be no direct path between the wireless device 210 and the AMF230 via which the NAS messages may be transported. The NAS messages maybe transported using the AS of the Uu and NG interfaces. The NASprotocols 217 and 237 may provide control plane functionality, such asauthentication, security, a connection setup, mobility management,session management, and/or any other functionality.

The RRCs 216 and 226 may provide/configure control plane functionalitybetween the wireless device 210 and the base station 220 and/or, moregenerally, between the wireless device 210 and the RAN (e.g., the basestation 220). The RRC layers 216 and 226 may provide/configure controlplane functionality between the wireless device 210 and the base station220 via signaling messages, which may be referred to as RRC messages.The RRC messages may be sent/transmitted between the wireless device 210and the RAN (e.g., the base station 220) using signaling radio bearersand the same/similar PDCP, RLC, MAC, and PHY protocol layers. The MAClayer may multiplex control-plane and user-plane data into the same TB.The RRC layers 216 and 226 may provide/configure control planefunctionality, such as one or more of the following functionalities:broadcast of system information related to AS and NAS; paging initiatedby the CN or the RAN; establishment, maintenance and release of an RRCconnection between the wireless device 210 and the RAN (e.g., the basestation 220); security functions including key management;establishment, configuration, maintenance and release of signaling radiobearers and data radio bearers; mobility functions; QoS managementfunctions; wireless device measurement reporting (e.g., the wirelessdevice measurement reporting) and control of the reporting; detection ofand recovery from radio link failure (RLF); and/or NAS message transfer.As part of establishing an RRC connection, RRC layers 216 and 226 mayestablish an RRC context, which may involve configuring parameters forcommunication between the wireless device 210 and the RAN (e.g., thebase station 220).

FIG. 6 shows example RRC states and RRC state transitions. An RRC stateof a wireless device may be changed to another RRC state (e.g., RRCstate transitions of a wireless device). The wireless device may besubstantially the same or similar to the wireless device 106, 210, orany other wireless device. A wireless device may be in at least one of aplurality of states, such as three RRC states comprising RRC connected602 (e.g., RRC_CONNECTED), RRC idle 606 (e.g., RRC_IDLE), and RRCinactive 604 (e.g., RRC_INACTIVE). The RRC inactive 604 may be RRCconnected but inactive.

An RRC connection may be established for the wireless device. Forexample, this may be during an RRC connected state. During the RRCconnected state (e.g., during the RRC connected 602), the wirelessdevice may have an established RRC context and may have at least one RRCconnection with a base station. The base station may be similar to oneof the one or more base stations (e.g., one or more base stations of theRAN 104 shown in FIG. 1A, one of the gNBs 160 or ng-eNBs 162 shown inFIG. 1B, the base station 220 shown in FIG. 2A and FIG. 2B, or any otherbase stations). The base station with which the wireless device isconnected (e.g., has established an RRC connection) may have the RRCcontext for the wireless device. The RRC context, which may be referredto as a wireless device context (e.g., the UE context), may compriseparameters for communication between the wireless device and the basestation. These parameters may comprise, for example, one or more of: AScontexts; radio link configuration parameters; bearer configurationinformation (e.g., relating to a data radio bearer, a signaling radiobearer, a logical channel, a QoS flow, and/or a PDU session); securityinformation; and/or layer configuration information (e.g., PHY, MAC,RLC, PDCP, and/or SDAP layer configuration information). During the RRCconnected state (e.g., the RRC connected 602), mobility of the wirelessdevice may be managed/controlled by an RAN (e.g., the RAN 104 or the NGRAN 154). The wireless device may measure received signal levels (e.g.,reference signal levels, reference signal received power, referencesignal received quality, received signal strength indicator, etc.) basedon one or more signals sent from a serving cell and neighboring cells.The wireless device may report these measurements to a serving basestation (e.g., the base station currently serving the wireless device).The serving base station of the wireless device may request a handoverto a cell of one of the neighboring base stations, for example, based onthe reported measurements. The RRC state may transition from the RRCconnected state (e.g., RRC connected 602) to an RRC idle state (e.g.,the RRC idle 606) via a connection release procedure 608. The RRC statemay transition from the RRC connected state (e.g., RRC connected 602) tothe RRC inactive state (e.g., RRC inactive 604) via a connectioninactivation procedure 610.

An RRC context may not be established for the wireless device. Forexample, this may be during the RRC idle state. During the RRC idlestate (e.g., the RRC idle 606), an RRC context may not be establishedfor the wireless device. During the RRC idle state (e.g., the RRC idle606), the wireless device may not have an RRC connection with the basestation. During the RRC idle state (e.g., the RRC idle 606), thewireless device may be in a sleep state for the majority of the time(e.g., to conserve battery power). The wireless device may wake upperiodically (e.g., each discontinuous reception (DRX) cycle) to monitorfor paging messages (e.g., paging messages set from the RAN). Mobilityof the wireless device may be managed by the wireless device via aprocedure of a cell reselection. The RRC state may transition from theRRC idle state (e.g., the RRC idle 606) to the RRC connected state(e.g., the RRC connected 602) via a connection establishment procedure612, which may involve a random access procedure.

A previously established RRC context may be maintained for the wirelessdevice. For example, this may be during the RRC inactive state. Duringthe RRC inactive state (e.g., the RRC inactive 604), the RRC contextpreviously established may be maintained in the wireless device and thebase station. The maintenance of the RRC context may enable/allow a fasttransition to the RRC connected state (e.g., the RRC connected 602) withreduced signaling overhead as compared to the transition from the RRCidle state (e.g., the RRC idle 606) to the RRC connected state (e.g.,the RRC connected 602). During the RRC inactive state (e.g., the RRCinactive 604), the wireless device may be in a sleep state and mobilityof the wireless device may be managed/controlled by the wireless devicevia a cell reselection. The RRC state may transition from the RRCinactive state (e.g., the RRC inactive 604) to the RRC connected state(e.g., the RRC connected 602) via a connection resume procedure 614. TheRRC state may transition from the RRC inactive state (e.g., the RRCinactive 604) to the RRC idle state (e.g., the RRC idle 606) via aconnection release procedure 616 that may be the same as or similar toconnection release procedure 608.

An RRC state may be associated with a mobility management mechanism.During the RRC idle state (e.g., RRC idle 606) and the RRC inactivestate (e.g., the RRC inactive 604), mobility may be managed/controlledby the wireless device via a cell reselection. The purpose of mobilitymanagement during the RRC idle state (e.g., the RRC idle 606) or duringthe RRC inactive state (e.g., the RRC inactive 604) may be toenable/allow the network to be able to notify the wireless device of anevent via a paging message without having to broadcast the pagingmessage over the entire mobile communications network. The mobilitymanagement mechanism used during the RRC idle state (e.g., the RRC idle606) or during the RRC idle state (e.g., the RRC inactive 604) mayenable/allow the network to track the wireless device on a cell-grouplevel, for example, so that the paging message may be broadcast over thecells of the cell group that the wireless device currently resideswithin (e.g. instead of sending the paging message over the entiremobile communication network). The mobility management mechanisms forthe RRC idle state (e.g., the RRC idle 606) and the RRC inactive state(e.g., the RRC inactive 604) may track the wireless device on acell-group level. The mobility management mechanisms may do thetracking, for example, using different granularities of grouping. Theremay be a plurality of levels of cell-grouping granularity (e.g., threelevels of cell-grouping granularity: individual cells; cells within aRAN area identified by a RAN area identifier (RAI); and cells within agroup of RAN areas, referred to as a tracking area and identified by atracking area identifier (TAI)).

Tracking areas may be used to track the wireless device (e.g., trackingthe location of the wireless device at the CN level). The CN (e.g., theCN 102, the 5G CN 152, or any other CN) may send to the wireless devicea list of TAIs associated with a wireless device registration area(e.g., a UE registration area). A wireless device may perform aregistration update with the CN to allow the CN to update the locationof the wireless device and provide the wireless device with a new the UEregistration area, for example, if the wireless device moves (e.g., viaa cell reselection) to a cell associated with a TAI that may not beincluded in the list of TAIs associated with the UE registration area.

RAN areas may be used to track the wireless device (e.g., the locationof the wireless device at the RAN level). For a wireless device in anRRC inactive state (e.g., the RRC inactive 604), the wireless device maybe assigned/provided/configured with a RAN notification area. A RANnotification area may comprise one or more cell identities (e.g., a listof RAIs and/or a list of TAIs). A base station may belong to one or moreRAN notification areas. A cell may belong to one or more RANnotification areas. A wireless device may perform a notification areaupdate with the RAN to update the RAN notification area of the wirelessdevice, for example, if the wireless device moves (e.g., via a cellreselection) to a cell not included in the RAN notification areaassigned/provided/configured to the wireless device.

A base station storing an RRC context for a wireless device or a lastserving base station of the wireless device may be referred to as ananchor base station. An anchor base station may maintain an RRC contextfor the wireless device at least during a period of time that thewireless device stays in a RAN notification area of the anchor basestation and/or during a period of time that the wireless device stays inan RRC inactive state (e.g., RRC inactive 604).

A base station (e.g., gNBs 160 in FIG. 1B or any other base station) maybe split in two parts: a central unit (e.g., a base station centralunit, such as a gNB CU) and one or more distributed units (e.g., a basestation distributed unit, such as a gNB DU). A base station central unit(CU) may be coupled to one or more base station distributed units (DUs)using an F1 interface (e.g., an F1 interface defined in an NRconfiguration). The base station CU may comprise the RRC, the PDCP, andthe SDAP layers. A base station distributed unit (DU) may comprise theRLC, the MAC, and the PHY layers.

The physical signals and physical channels (e.g., described with respectto FIG. 5A and FIG. 5B) may be mapped onto one or more symbols (e.g.,orthogonal frequency divisional multiplexing (OFDM) symbols in an NRconfiguration or any other symbols). OFDM is a multicarriercommunication scheme that sends/transmits data over F orthogonalsubcarriers (or tones). The data may be mapped to a series of complexsymbols (e.g., M-quadrature amplitude modulation (M-QAM) symbols orM-phase shift keying (M PSK) symbols or any other modulated symbols),referred to as source symbols, and divided into F parallel symbolstreams, for example, before transmission of the data. The F parallelsymbol streams may be treated as if they are in the frequency domain.The F parallel symbols may be used as inputs to an Inverse Fast FourierTransform (IFFT) block that transforms them into the time domain. TheIFFT block may take in F source symbols at a time, one from each of theF parallel symbol streams. The IFFT block may use each source symbol tomodulate the amplitude and phase of one of F sinusoidal basis functionsthat correspond to the F orthogonal subcarriers. The output of the IFFTblock may be F time-domain samples that represent the summation of the Forthogonal subcarriers. The F time-domain samples may form a single OFDMsymbol. An OFDM symbol provided/output by the IFFT block may besent/transmitted over the air interface on a carrier frequency, forexample, after one or more processes (e.g., addition of a cyclic prefix)and up-conversion. The F parallel symbol streams may be mixed, forexample, using a Fast Fourier Transform (FFT) block before beingprocessed by the IFFT block. This operation may produce Discrete FourierTransform (DFT)-precoded OFDM symbols and may be used by one or morewireless devices in the uplink to reduce the peak to average power ratio(PAPR). Inverse processing may be performed on the OFDM symbol at areceiver using an FFT block to recover the data mapped to the sourcesymbols.

FIG. 7 shows an example configuration of a frame. The frame maycomprise, for example, an NR radio frame into which OFDM symbols may begrouped. A frame (e.g., an NR radio frame) may be identified/indicatedby a system frame number (SFN) or any other value. The SFN may repeatwith a period of 1024 frames. One NR frame may be 10 milliseconds (ms)in duration and may comprise 10 subframes that are 1 ms in duration. Asubframe may be divided into one or more slots (e.g., depending onnumerologies and/or different subcarrier spacings). Each of the one ormore slots may comprise, for example, 14 OFDM symbols per slot. Anyquantity of symbols, slots, or duration may be used for any timeinterval.

The duration of a slot may depend on the numerology used for the OFDMsymbols of the slot. A flexible numerology may be supported, forexample, to accommodate different deployments (e.g., cells with carrierfrequencies below 1 GHz up to cells with carrier frequencies in themm-wave range). A flexible numerology may be supported, for example, inan NR configuration or any other radio configurations. A numerology maybe defined in terms of subcarrier spacing and/or cyclic prefix duration.Subcarrier spacings may be scaled up by powers of two from a baselinesubcarrier spacing of 15 kHz. Cyclic prefix durations may be scaled downby powers of two from a baseline cyclic prefix duration of 4.7 μs, forexample, for a numerology in an NR configuration or any other radioconfigurations. Numerologies may be defined with the followingsubcarrier spacing/cyclic prefix duration combinations: 15 kHz/4.7 μs;30 kHz/2.3 μs; 60 kHz/1.2 μs; 120 kHz/0.59 μs; 240 kHz/0.29 μs, and/orany other subcarrier spacing/cyclic prefix duration combinations.

A slot may have a fixed number/quantity of OFDM symbols (e.g., 14 OFDMsymbols). A numerology with a higher subcarrier spacing may have ashorter slot duration and more slots per subframe. Examples ofnumerology-dependent slot duration and slots-per-subframe transmissionstructure are shown in FIG. 7 (the numerology with a subcarrier spacingof 240 kHz is not shown in FIG. 7 ). A subframe (e.g., in an NRconfiguration) may be used as a numerology-independent time reference. Aslot may be used as the unit upon which uplink and downlinktransmissions are scheduled. Scheduling (e.g., in an NR configuration)may be decoupled from the slot duration. Scheduling may start at anyOFDM symbol. Scheduling may last for as many symbols as needed for atransmission, for example, to support low latency. These partial slottransmissions may be referred to as mini-slot or sub-slot transmissions.

FIG. 8 shows an example resource configuration of one or more carriers.The resource configuration of may comprise a slot in the time andfrequency domain for an NR carrier or any other carrier. The slot maycomprise resource elements (REs) and resource blocks (RBs). A resourceelement (RE) may be the smallest physical resource (e.g., in an NRconfiguration). An RE may span one OFDM symbol in the time domain by onesubcarrier in the frequency domain, such as shown in FIG. 8 . An RB mayspan twelve consecutive REs in the frequency domain, such as shown inFIG. 8 . A carrier (e.g., an NR carrier) may be limited to a width of acertain quantity of RBs and/or subcarriers (e.g., 275 RBs or 275×12=3300subcarriers). Such limitation(s), if used, may limit the carrier (e.g.,NR carrier) frequency based on subcarrier spacing (e.g., carrierfrequency of 50, 100, 200, and 400 MHz for subcarrier spacings of 15,30, 60, and 120 kHz, respectively). A 400 MHz bandwidth may be set basedon a 400 MHz per carrier bandwidth limit. Any other bandwidth may be setbased on a per carrier bandwidth limit.

A single numerology may be used across the entire bandwidth of a carrier(e.g., an NR such as shown in FIG. 8 ). In other example configurations,multiple numerologies may be supported on the same carrier. NR and/orother access technologies may support wide carrier bandwidths (e.g., upto 400 MHz for a subcarrier spacing of 120 kHz). Not all wirelessdevices may be able to receive the full carrier bandwidth (e.g., due tohardware limitations and/or different wireless device capabilities).Receiving and/or utilizing the full carrier bandwidth may beprohibitive, for example, in terms of wireless device power consumption.A wireless device may adapt the size of the receive bandwidth of thewireless device, for example, based on the amount of traffic thewireless device is scheduled to receive (e.g., to reduce powerconsumption and/or for other purposes). Such an adaptation may bereferred to as bandwidth adaptation.

Configuration of one or more bandwidth parts (BWPs) may support one ormore wireless devices not capable of receiving the full carrierbandwidth. BWPs may support bandwidth adaptation, for example, for suchwireless devices not capable of receiving the full carrier bandwidth. ABWP (e.g., a BWP of an NR configuration) may be defined by a subset ofcontiguous RBs on a carrier. A wireless device may be configured (e.g.,via an RRC layer) with one or more downlink BWPs per serving cell andone or more uplink BWPs per serving cell (e.g., up to four downlink BWPsper serving cell and up to four uplink BWPs per serving cell). One ormore of the configured BWPs for a serving cell may be active, forexample, at a given time. The one or more BWPs may be referred to asactive BWPs of the serving cell. A serving cell may have one or morefirst active BWPs in the uplink carrier and one or more second activeBWPs in the secondary uplink carrier, for example, if the serving cellis configured with a secondary uplink carrier.

A downlink BWP from a set of configured downlink BWPs may be linked withan uplink BWP from a set of configured uplink BWPs (e.g., for unpairedspectra). A downlink BWP and an uplink BWP may be linked, for example,if a downlink BWP index of the downlink BWP and an uplink BWP index ofthe uplink BWP are the same. A wireless device may expect that thecenter frequency for a downlink BWP is the same as the center frequencyfor an uplink BWP (e.g., for unpaired spectra).

A base station may configure a wireless device with one or more controlresource sets (CORESETs) for at least one search space. The base stationmay configure the wireless device with one or more CORESETS, forexample, for a downlink BWP in a set of configured downlink BWPs on aprimary cell (PCell) or on a secondary cell (SCell). A search space maycomprise a set of locations in the time and frequency domains where thewireless device may monitor/find/detect/identify control information.The search space may be a wireless device-specific search space (e.g., aUE-specific search space) or a common search space (e.g., potentiallyusable by a plurality of wireless devices or a group of wireless userdevices). A base station may configure a group of wireless devices witha common search space, on a PCell or on a primary secondary cell(PSCell), in an active downlink BWP.

A base station may configure a wireless device with one or more resourcesets for one or more PUCCH transmissions, for example, for an uplink BWPin a set of configured uplink BWPs. A wireless device may receivedownlink receptions (e.g., PDCCH or PDSCH) in a downlink BWP, forexample, according to a configured numerology (e.g., a configuredsubcarrier spacing and/or a configured cyclic prefix duration) for thedownlink BWP. The wireless device may send/transmit uplink transmissions(e.g., PUCCH or PUSCH) in an uplink BWP, for example, according to aconfigured numerology (e.g., a configured subcarrier spacing and/or aconfigured cyclic prefix length for the uplink BWP).

One or more BWP indicator fields may be provided/comprised in DownlinkControl Information (DCI). A value of a BWP indicator field may indicatewhich BWP in a set of configured BWPs is an active downlink BWP for oneor more downlink receptions. The value of the one or more BWP indicatorfields may indicate an active uplink BWP for one or more uplinktransmissions.

A base station may semi-statically configure a wireless device with adefault downlink BWP within a set of configured downlink BWPs associatedwith a PCell. A default downlink BWP may be an initial active downlinkBWP, for example, if the base station does not provide/configure adefault downlink BWP to/for the wireless device. The wireless device maydetermine which BWP is the initial active downlink BWP, for example,based on a CORESET configuration obtained using the PBCH.

A base station may configure a wireless device with a BWP inactivitytimer value for a PCell. The wireless device may start or restart a BWPinactivity timer at any appropriate time. The wireless device may startor restart the BWP inactivity timer, for example, if one or moreconditions are satisfied. The one or more conditions may comprise atleast one of: the wireless device detects DCI indicating an activedownlink BWP other than a default downlink BWP for a paired spectraoperation; the wireless device detects DCI indicating an active downlinkBWP other than a default downlink BWP for an unpaired spectra operation;and/or the wireless device detects DCI indicating an active uplink BWPother than a default uplink BWP for an unpaired spectra operation. Thewireless device may start/run the BWP inactivity timer toward expiration(e.g., increment from zero to the BWP inactivity timer value, ordecrement from the BWP inactivity timer value to zero), for example, ifthe wireless device does not detect DCI during a time interval (e.g., 1ms or 0.5 ms). The wireless device may switch from the active downlinkBWP to the default downlink BWP, for example, if the BWP inactivitytimer expires.

A base station may semi-statically configure a wireless device with oneor more BWPs. A wireless device may switch an active BWP from a firstBWP to a second BWP, for example, after (e.g., based on or in responseto) receiving DCI indicating the second BWP as an active BWP. A wirelessdevice may switch an active BWP from a first BWP to a second BWP, forexample, after (e.g., based on or in response to) an expiry of the BWPinactivity timer (e.g., if the second BWP is the default BWP).

A downlink BWP switching may refer to switching an active downlink BWPfrom a first downlink BWP to a second downlink BWP (e.g., the seconddownlink BWP is activated and the first downlink BWP is deactivated). Anuplink BWP switching may refer to switching an active uplink BWP from afirst uplink BWP to a second uplink BWP (e.g., the second uplink BWP isactivated and the first uplink BWP is deactivated). Downlink and uplinkBWP switching may be performed independently (e.g., in pairedspectrum/spectra). Downlink and uplink BWP switching may be performedsimultaneously (e.g., in unpaired spectrum/spectra). Switching betweenconfigured BWPs may occur, for example, based on RRC signaling, DCIsignaling, expiration of a BWP inactivity timer, and/or an initiation ofrandom access.

FIG. 9 shows an example of configured BWPs. Bandwidth adaptation usingmultiple BWPs (e.g., three configured BWPs for an NR carrier) may beavailable. A wireless device configured with multiple BWPs (e.g., thethree BWPs) may switch from one BWP to another BWP at a switching point.The BWPs may comprise: a BWP 902 having a bandwidth of 40 MHz and asubcarrier spacing of 15 kHz; a BWP 904 having a bandwidth of 10 MHz anda subcarrier spacing of 15 kHz; and a BWP 906 having a bandwidth of 20MHz and a subcarrier spacing of 60 kHz. The BWP 902 may be an initialactive BWP, and the BWP 904 may be a default BWP. The wireless devicemay switch between BWPs at switching points. The wireless device mayswitch from the BWP 902 to the BWP 904 at a switching point 908. Theswitching at the switching point 908 may occur for any suitable reasons.The switching at a switching point 908 may occur, for example, after(e.g., based on or in response to) an expiry of a BWP inactivity timer(e.g., indicating switching to the default BWP). The switching at theswitching point 908 may occur, for example, after (e.g., based on or inresponse to) receiving DCI indicating BWP 904 as the active BWP. Thewireless device may switch at a switching point 910 from an active BWP904 to the BWP 906, for example, after or in response receiving DCIindicating BWP 906 as a new active BWP. The wireless device may switchat a switching point 912 from an active BWP 906 to the BWP 904, forexample, after (e.g., based on or in response to) an expiry of a BWPinactivity timer. The wireless device may switch at the switching point912 from an active BWP 906 to the BWP 904, for example, after or inresponse receiving DCI indicating BWP 904 as a new active BWP. Thewireless device may switch at a switching point 914 from an active BWP904 to the BWP 902, for example, after or in response receiving DCIindicating the BWP 902 as a new active BWP.

Wireless device procedures for switching BWPs on a secondary cell may bethe same/similar as those on a primary cell, for example, if thewireless device is configured for a secondary cell with a defaultdownlink BWP in a set of configured downlink BWPs and a timer value. Thewireless device may use the timer value and the default downlink BWP forthe secondary cell in the same/similar manner as the wireless deviceuses the timer value and/or default BWPs for a primary cell. The timervalue (e.g., the BWP inactivity timer) may be configured per cell (e.g.,for one or more BWPs), for example, via RRC signaling or any othersignaling. One or more active BWPs may switch to another BWP, forexample, based on an expiration of the BWP inactivity timer.

Two or more carriers may be aggregated and data may be simultaneouslysent/transmitted to/from the same wireless device using carrieraggregation (CA) (e.g., to increase data rates). The aggregated carriersin CA may be referred to as component carriers (CCs). There may be anumber/quantity of serving cells for the wireless device (e.g., oneserving cell for a CC), for example, if CA is configured/used. The CCsmay have multiple configurations in the frequency domain.

FIG. 10A shows example CA configurations based on CCs. As shown in FIG.10A, three types of CA configurations may comprise an intraband(contiguous) configuration 1002, an intraband (non-contiguous)configuration 1004, and/or an interband configuration 1006. In theintraband (contiguous) configuration 1002, two CCs may be aggregated inthe same frequency band (frequency band A) and may be located directlyadjacent to each other within the frequency band. In the intraband(non-contiguous) configuration 1004, two CCs may be aggregated in thesame frequency band (frequency band A) but may be separated from eachother in the frequency band by a gap. In the interband configuration1006, two CCs may be located in different frequency bands (e.g.,frequency band A and frequency band B, respectively).

A network may set the maximum quantity of CCs that can be aggregated(e.g., up to 32 CCs may be aggregated in NR, or any other quantity maybe aggregated in other systems). The aggregated CCs may have the same ordifferent bandwidths, subcarrier spacing, and/or duplexing schemes (TDD,FDD, or any other duplexing schemes). A serving cell for a wirelessdevice using CA may have a downlink CC. One or more uplink CCs may beoptionally configured for a serving cell (e.g., for FDD). The ability toaggregate more downlink carriers than uplink carriers may be useful, forexample, if the wireless device has more data traffic in the downlinkthan in the uplink.

One of the aggregated cells for a wireless device may be referred to asa primary cell (PCell), for example, if a CA is configured. The PCellmay be the serving cell that the wireless initially connects to oraccess to, for example, during or at an RRC connection establishment, anRRC connection reestablishment, and/or a handover. The PCell mayprovide/configure the wireless device with NAS mobility information andthe security input. Wireless device may have different PCells. For thedownlink, the carrier corresponding to the PCell may be referred to asthe downlink primary CC (DL PCC). For the uplink, the carriercorresponding to the PCell may be referred to as the uplink primary CC(UL PCC). The other aggregated cells (e.g., associated with CCs otherthan the DL PCC and UL PCC) for the wireless device may be referred toas secondary cells (SCells). The SCells may be configured, for example,after the PCell is configured for the wireless device. An SCell may beconfigured via an RRC connection reconfiguration procedure. For thedownlink, the carrier corresponding to an SCell may be referred to as adownlink secondary CC (DL SCC). For the uplink, the carriercorresponding to the SCell may be referred to as the uplink secondary CC(UL SCC).

Configured SCells for a wireless device may be activated or deactivated,for example, based on traffic and channel conditions. Deactivation of anSCell may cause the wireless device to stop PDCCH and PDSCH reception onthe SCell and PUSCH, SRS, and CQI transmissions on the SCell. ConfiguredSCells may be activated or deactivated, for example, using a MAC CE(e.g., the MAC CE described with respect to FIG. 4B). A MAC CE may use abitmap (e.g., one bit per SCell) to indicate which SCells (e.g., in asubset of configured SCells) for the wireless device are activated ordeactivated. Configured SCells may be deactivated, for example, after(e.g., based on or in response to) an expiration of an SCelldeactivation timer (e.g., one SCell deactivation timer per SCell may beconfigured).

DCI may comprise control information, such as scheduling assignments andscheduling grants, for a cell. DCI may be sent/transmitted via the cellcorresponding to the scheduling assignments and/or scheduling grants,which may be referred to as a self-scheduling. DCI comprising controlinformation for a cell may be sent/transmitted via another cell, whichmay be referred to as a cross-carrier scheduling. Uplink controlinformation (UCI) may comprise control information, such as HARQacknowledgments and channel state feedback (e.g., CQI, PMI, and/or RI)for aggregated cells. UCI may be sent/transmitted via an uplink controlchannel (e.g., a PUCCH) of the PCell or a certain SCell (e.g., an SCellconfigured with PUCCH). For a larger number of aggregated downlink CCs,the PUCCH of the PCell may become overloaded. Cells may be divided intomultiple PUCCH groups.

FIG. 10B shows example group of cells. Aggregated cells may beconfigured into one or more PUCCH groups (e.g., as shown in FIG. 10B).One or more cell groups or one or more uplink control channel groups(e.g., a PUCCH group 1010 and a PUCCH group 1050) may comprise one ormore downlink CCs, respectively. The PUCCH group 1010 may comprise oneor more downlink CCs, for example, three downlink CCs: a PCell 1011(e.g., a DL PCC), an SCell 1012 (e.g., a DL SCC), and an SCell 1013(e.g., a DL SCC). The PUCCH group 1050 may comprise one or more downlinkCCs, for example, three downlink CCs: a PUCCH SCell (or PSCell) 1051(e.g., a DL SCC), an SCell 1052 (e.g., a DL SCC), and an SCell 1053(e.g., a DL SCC). One or more uplink CCs of the PUCCH group 1010 may beconfigured as a PCell 1021 (e.g., a UL PCC), an SCell 1022 (e.g., a ULSCC), and an SCell 1023 (e.g., a UL SCC). One or more uplink CCs of thePUCCH group 1050 may be configured as a PUCCH SCell (or PSCell) 1061(e.g., a UL SCC), an SCell 1062 (e.g., a UL SCC), and an SCell 1063(e.g., a UL SCC). UCI related to the downlink CCs of the PUCCH group1010, shown as UCI 1031, UCI 1032, and UCI 1033, may be sent/transmittedvia the uplink of the PCell 1021 (e.g., via the PUCCH of the PCell1021). UCI related to the downlink CCs of the PUCCH group 1050, shown asUCI 1071, UCI 1072, and UCI 1073, may be sent/transmitted via the uplinkof the PUCCH SCell (or PSCell) 1061 (e.g., via the PUCCH of the PUCCHSCell 1061). A single uplink PCell may be configured to send/transmitUCI relating to the six downlink CCs, for example, if the aggregatedcells shown in FIG. 10B are not divided into the PUCCH group 1010 andthe PUCCH group 1050. The PCell 1021 may become overloaded, for example,if the UCIs 1031, 1032, 1033, 1071, 1072, and 1073 are sent/transmittedvia the PCell 1021. By dividing transmissions of UCI between the PCell1021 and the PUCCH SCell (or PSCell) 1061, overloading may be preventedand/or reduced.

A PCell may comprise a downlink carrier (e.g., the PCell 1011) and anuplink carrier (e.g., the PCell 1021). An SCell may comprise only adownlink carrier. A cell, comprising a downlink carrier and optionallyan uplink carrier, may be assigned with a physical cell ID and a cellindex. The physical cell ID or the cell index may indicate/identify adownlink carrier and/or an uplink carrier of the cell, for example,depending on the context in which the physical cell ID is used. Aphysical cell ID may be determined, for example, using a synchronizationsignal (e.g., PSS and/or SSS) sent/transmitted via a downlink componentcarrier. A cell index may be determined, for example, using one or moreRRC messages. A physical cell ID may be referred to as a carrier ID, anda cell index may be referred to as a carrier index. A first physicalcell ID for a first downlink carrier may refer to the first physicalcell ID for a cell comprising the first downlink carrier. Substantiallythe same/similar concept may apply to, for example, a carrieractivation. Activation of a first carrier may refer to activation of acell comprising the first carrier.

A multi-carrier nature of a PHY layer may be exposed/indicated to a MAClayer (e.g., in a CA configuration). A HARQ entity may operate on aserving cell. A transport block may be generated per assignment/grantper serving cell. A transport block and potential HARQ retransmissionsof the transport block may be mapped to a serving cell.

For the downlink, a base station may send/transmit (e.g., unicast,multicast, and/or broadcast), to one or more wireless devices, one ormore reference signals (RSs) (e.g., PSS, SSS, CSI-RS, DM-RS, and/orPT-RS). For the uplink, the one or more wireless devices maysend/transmit one or more RSs to the base station (e.g., DM-RS, PT-RS,and/or SRS). The PSS and the SSS may be sent/transmitted by the basestation and used by the one or more wireless devices to synchronize theone or more wireless devices with the base station. A synchronizationsignal (SS)/physical broadcast channel (PBCH) block may comprise thePSS, the SSS, and the PBCH. The base station may periodicallysend/transmit a burst of SS/PBCH blocks, which may be referred to asSSBs.

FIG. 11A shows an example mapping of one or more SS/PBCH blocks. A burstof SS/PBCH blocks may comprise one or more SS/PBCH blocks (e.g., 4SS/PBCH blocks, as shown in FIG. 11A). Bursts may be sent/transmittedperiodically (e.g., every 2 frames, 20 ms, or any other durations). Aburst may be restricted to a half-frame (e.g., a first half-frame havinga duration of 5 ms). Such parameters (e.g., the number of SS/PBCH blocksper burst, periodicity of bursts, position of the burst within theframe) may be configured, for example, based on at least one of: acarrier frequency of a cell in which the SS/PBCH block issent/transmitted; a numerology or subcarrier spacing of the cell; aconfiguration by the network (e.g., using RRC signaling); and/or anyother suitable factor(s). A wireless device may assume a subcarrierspacing for the SS/PBCH block based on the carrier frequency beingmonitored, for example, unless the radio network configured the wirelessdevice to assume a different subcarrier spacing.

The SS/PBCH block may span one or more OFDM symbols in the time domain(e.g., 4 OFDM symbols, as shown in FIG. 11A or any other quantity/numberof symbols) and may span one or more subcarriers in the frequency domain(e.g., 240 contiguous subcarriers or any other quantity/number ofsubcarriers). The PSS, the SSS, and the PBCH may have a common centerfrequency. The PSS may be sent/transmitted first and may span, forexample, 1 OFDM symbol and 127 subcarriers. The SSS may besent/transmitted after the PSS (e.g., two symbols later) and may span 1OFDM symbol and 127 subcarriers. The PBCH may be sent/transmitted afterthe PSS (e.g., across the next 3 OFDM symbols) and may span 240subcarriers (e.g., in the second and fourth OFDM symbols as shown inFIG. 11A) and/or may span fewer than 240 subcarriers (e.g., in the thirdOFDM symbols as shown in FIG. 11A).

The location of the SS/PBCH block in the time and frequency domains maynot be known to the wireless device (e.g., if the wireless device issearching for the cell). The wireless device may monitor a carrier forthe PSS, for example, to find and select the cell. The wireless devicemay monitor a frequency location within the carrier. The wireless devicemay search for the PSS at a different frequency location within thecarrier, for example, if the PSS is not found after a certain duration(e.g., 20 ms). The wireless device may search for the PSS at a differentfrequency location within the carrier, for example, as indicated by asynchronization raster. The wireless device may determine the locationsof the SSS and the PBCH, respectively, for example, based on a knownstructure of the SS/PBCH block if the PSS is found at a location in thetime and frequency domains. The SS/PBCH block may be a cell-defining SSblock (CD-SSB). A primary cell may be associated with a CD-SSB. TheCD-SSB may be located on a synchronization raster. A cellselection/search and/or reselection may be based on the CD-SSB.

The SS/PBCH block may be used by the wireless device to determine one ormore parameters of the cell. The wireless device may determine aphysical cell identifier (PCI) of the cell, for example, based on thesequences of the PSS and the SSS, respectively. The wireless device maydetermine a location of a frame boundary of the cell, for example, basedon the location of the SS/PBCH block. The SS/PBCH block may indicatethat it has been sent/transmitted in accordance with a transmissionpattern. An SS/PBCH block in the transmission pattern may be a knowndistance from the frame boundary (e.g., a predefined distance for a RANconfiguration among one or more networks, one or more base stations, andone or more wireless devices).

The PBCH may use a QPSK modulation and/or forward error correction(FEC). The FEC may use polar coding. One or more symbols spanned by thePBCH may comprise/carry one or more DM-RSs for demodulation of the PBCH.The PBCH may comprise an indication of a current system frame number(SFN) of the cell and/or a SS/PBCH block timing index. These parametersmay facilitate time synchronization of the wireless device to the basestation. The PBCH may comprise a MIB used to send/transmit to thewireless device one or more parameters. The MIB may be used by thewireless device to locate remaining minimum system information (RMSI)associated with the cell. The RMSI may comprise a System InformationBlock Type 1 (SIB1). The SIB1 may comprise information for the wirelessdevice to access the cell. The wireless device may use one or moreparameters of the MIB to monitor a PDCCH, which may be used to schedulea PDSCH. The PDSCH may comprise the SIB1. The SIB1 may be decoded usingparameters provided/comprised in the MIB. The PBCH may indicate anabsence of SIB1. The wireless device may be pointed to a frequency, forexample, based on the PBCH indicating the absence of SIB1. The wirelessdevice may search for an SS/PBCH block at the frequency to which thewireless device is pointed.

The wireless device may assume that one or more SS/PBCH blockssent/transmitted with a same SS/PBCH block index are quasi co-located(QCLed) (e.g., having substantially the same/similar Doppler spread,Doppler shift, average gain, average delay, and/or spatial Rxparameters). The wireless device may not assume QCL for SS/PBCH blocktransmissions having different SS/PBCH block indices. SS/PBCH blocks(e.g., those within a half-frame) may be sent/transmitted in spatialdirections (e.g., using different beams that span a coverage area of thecell). A first SS/PBCH block may be sent/transmitted in a first spatialdirection using a first beam, a second SS/PBCH block may besent/transmitted in a second spatial direction using a second beam, athird SS/PBCH block may be sent/transmitted in a third spatial directionusing a third beam, a fourth SS/PBCH block may be sent/transmitted in afourth spatial direction using a fourth beam, etc.

A base station may send/transmit a plurality of SS/PBCH blocks, forexample, within a frequency span of a carrier. A first PCI of a firstSS/PBCH block of the plurality of SS/PBCH blocks may be different from asecond PCI of a second SS/PBCH block of the plurality of SS/PBCH blocks.The PCIs of SS/PBCH blocks sent/transmitted in different frequencylocations may be different or substantially the same.

The CSI-RS may be sent/transmitted by the base station and used by thewireless device to acquire/obtain/determine channel state information(CSI). The base station may configure the wireless device with one ormore CSI-RSs for channel estimation or any other suitable purpose. Thebase station may configure a wireless device with one or more of thesame/similar CSI-RSs. The wireless device may measure the one or moreCSI-RSs. The wireless device may estimate a downlink channel stateand/or generate a CSI report, for example, based on the measuring of theone or more downlink CSI-RSs. The wireless device may send/transmit theCSI report to the base station (e.g., based on periodic CSI reporting,semi-persistent CSI reporting, and/or aperiodic CSI reporting). The basestation may use feedback provided by the wireless device (e.g., theestimated downlink channel state) to perform a link adaptation.

The base station may semi-statically configure the wireless device withone or more CSI-RS resource sets. A CSI-RS resource may be associatedwith a location in the time and frequency domains and a periodicity. Thebase station may selectively activate and/or deactivate a CSI-RSresource. The base station may indicate to the wireless device that aCSI-RS resource in the CSI-RS resource set is activated and/ordeactivated.

The base station may configure the wireless device to report CSImeasurements. The base station may configure the wireless device toprovide CSI reports periodically, aperiodically, or semi-persistently.For periodic CSI reporting, the wireless device may be configured with atiming and/or periodicity of a plurality of CSI reports. For aperiodicCSI reporting, the base station may request a CSI report. The basestation may command the wireless device to measure a configured CSI-RSresource and provide a CSI report relating to the measurement(s). Forsemi-persistent CSI reporting, the base station may configure thewireless device to send/transmit periodically, and selectively activateor deactivate the periodic reporting (e.g., via one or moreactivation/deactivation MAC CEs and/or one or more DCIs). The basestation may configure the wireless device with a CSI-RS resource set andCSI reports, for example, using RRC signaling.

The CSI-RS configuration may comprise one or more parameters indicating,for example, up to 32 antenna ports (or any other quantity of antennaports). The wireless device may be configured to use/employ the sameOFDM symbols for a downlink CSI-RS and a CORESET, for example, if thedownlink CSI-RS and CORESET are spatially QCLed and resource elementsassociated with the downlink CSI-RS are outside of the physical resourceblocks (PRBs) configured for the CORESET. The wireless device may beconfigured to use/employ the same OFDM symbols for a downlink CSI-RS andSS/PBCH blocks, for example, if the downlink CSI-RS and SS/PBCH blocksare spatially QCLed and resource elements associated with the downlinkCSI-RS are outside of PRBs configured for the SS/PBCH blocks.

Downlink DM-RSs may be sent/transmitted by a base station andreceived/used by a wireless device for a channel estimation. Thedownlink DM-RSs may be used for coherent demodulation of one or moredownlink physical channels (e.g., PDSCH). A network (e.g., an NRnetwork) may support one or more variable and/or configurable DM-RSpatterns for data demodulation. At least one downlink DM-RSconfiguration may support a front-loaded DM-RS pattern. A front-loadedDM-RS may be mapped over one or more OFDM symbols (e.g., one or twoadjacent OFDM symbols). A base station may semi-statically configure thewireless device with a number/quantity (e.g. a maximum number/quantity)of front-loaded DM-RS symbols for a PDSCH. A DM-RS configuration maysupport one or more DM-RS ports. A DM-RS configuration may support up toeight orthogonal downlink DM-RS ports per wireless device (e.g., forsingle user-MIMO). A DM-RS configuration may support up to 4 orthogonaldownlink DM-RS ports per wireless device (e.g., for multiuser-MIMO). Aradio network may support (e.g., at least for CP-OFDM) a common DM-RSstructure for downlink and uplink. A DM-RS location, a DM-RS pattern,and/or a scrambling sequence may be the same or different. The basestation may send/transmit a downlink DM-RS and a corresponding PDSCH,for example, using the same precoding matrix. The wireless device mayuse the one or more downlink DM-RSs for coherent demodulation/channelestimation of the PDSCH.

A transmitter (e.g., a transmitter of a base station) may use a precodermatrices for a part of a transmission bandwidth. The transmitter may usea first precoder matrix for a first bandwidth and a second precodermatrix for a second bandwidth. The first precoder matrix and the secondprecoder matrix may be different, for example, based on the firstbandwidth being different from the second bandwidth. The wireless devicemay assume that a same precoding matrix is used across a set of PRBs.The set of PRBs may be determined/indicated/identified/denoted as aprecoding resource block group (PRG).

A PDSCH may comprise one or more layers. The wireless device may assumethat at least one symbol with DM-RS is present on a layer of the one ormore layers of the PDSCH. A higher layer may configure one or moreDM-RSs for a PDSCH (e.g., up to 3 DMRSs for the PDSCH). Downlink PT-RSmay be sent/transmitted by a base station and used by a wireless device,for example, for a phase-noise compensation. Whether a downlink PT-RS ispresent or not may depend on an RRC configuration. The presence and/orthe pattern of the downlink PT-RS may be configured on a wirelessdevice-specific basis, for example, using a combination of RRC signalingand/or an association with one or more parameters used/employed forother purposes (e.g., modulation and coding scheme (MCS)), which may beindicated by DCI. A dynamic presence of a downlink PT-RS, if configured,may be associated with one or more DCI parameters comprising at leastMCS. A network (e.g., an NR network) may support a plurality of PT-RSdensities defined in the time and/or frequency domains. A frequencydomain density (if configured/present) may be associated with at leastone configuration of a scheduled bandwidth. The wireless device mayassume a same precoding for a DM-RS port and a PT-RS port. Thequantity/number of PT-RS ports may be fewer than the quantity/number ofDM-RS ports in a scheduled resource. Downlink PT-RS may beconfigured/allocated/confined in the scheduled time/frequency durationfor the wireless device. Downlink PT-RS may be sent/transmitted viasymbols, for example, to facilitate a phase tracking at the receiver.

The wireless device may send/transmit an uplink DM-RS to a base station,for example, for a channel estimation. The base station may use theuplink DM-RS for coherent demodulation of one or more uplink physicalchannels. The wireless device may send/transmit an uplink DM-RS with aPUSCH and/or a PUCCH. The uplink DM-RS may span a range of frequenciesthat is similar to a range of frequencies associated with thecorresponding physical channel. The base station may configure thewireless device with one or more uplink DM-RS configurations. At leastone DM-RS configuration may support a front-loaded DM-RS pattern. Thefront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g.,one or two adjacent OFDM symbols). One or more uplink DM-RSs may beconfigured to send/transmit at one or more symbols of a PUSCH and/or aPUCCH. The base station may semi-statically configure the wirelessdevice with a number/quantity (e.g. the maximum number/quantity) offront-loaded DM-RS symbols for the PUSCH and/or the PUCCH, which thewireless device may use to schedule a single-symbol DM-RS and/or adouble-symbol DM-RS. A network (e.g., an NR network) may support (e.g.,for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM))a common DM-RS structure for downlink and uplink. A DM-RS location, aDM-RS pattern, and/or a scrambling sequence for the DM-RS may besubstantially the same or different.

A PUSCH may comprise one or more layers. A wireless device maysend/transmit at least one symbol with DM-RS present on a layer of theone or more layers of the PUSCH. A higher layer may configure one ormore DM-RSs (e.g., up to three DMRSs) for the PUSCH. Uplink PT-RS (whichmay be used by a base station for a phase tracking and/or a phase-noisecompensation) may or may not be present, for example, depending on anRRC configuration of the wireless device. The presence and/or thepattern of an uplink PT-RS may be configured on a wirelessdevice-specific basis (e.g., a UE-specific basis), for example, by acombination of RRC signaling and/or one or more parametersconfigured/employed for other purposes (e.g., MCS), which may beindicated by DCI. A dynamic presence of an uplink PT-RS, if configured,may be associated with one or more DCI parameters comprising at leastMCS. A radio network may support a plurality of uplink PT-RS densitiesdefined in time/frequency domain. A frequency domain density (ifconfigured/present) may be associated with at least one configuration ofa scheduled bandwidth. The wireless device may assume a same precodingfor a DM-RS port and a PT-RS port. A quantity/number of PT-RS ports maybe less than a quantity/number of DM-RS ports in a scheduled resource.An uplink PT-RS may be configured/allocated/confined in the scheduledtime/frequency duration for the wireless device.

One or more SRSs may be sent/transmitted by a wireless device to a basestation, for example, for a channel state estimation to support uplinkchannel dependent scheduling and/or a link adaptation. SRSsent/transmitted by the wireless device may enable/allow a base stationto estimate an uplink channel state at one or more frequencies. Ascheduler at the base station may use/employ the estimated uplinkchannel state to assign one or more resource blocks for an uplink PUSCHtransmission for the wireless device. The base station maysemi-statically configure the wireless device with one or more SRSresource sets. For an SRS resource set, the base station may configurethe wireless device with one or more SRS resources. An SRS resource setapplicability may be configured, for example, by a higher layer (e.g.,RRC) parameter. An SRS resource in a SRS resource set of the one or moreSRS resource sets (e.g., with the same/similar time domain behavior,periodic, aperiodic, and/or the like) may be sent/transmitted at a timeinstant (e.g., simultaneously), for example, if a higher layer parameterindicates beam management. The wireless device may send/transmit one ormore SRS resources in SRS resource sets. A network (e.g., an NR network)may support aperiodic, periodic, and/or semi-persistent SRStransmissions. The wireless device may send/transmit SRS resources, forexample, based on one or more trigger types. The one or more triggertypes may comprise higher layer signaling (e.g., RRC) and/or one or moreDCI formats. At least one DCI format may be used/employed for thewireless device to select at least one of one or more configured SRSresource sets. An SRS trigger type 0 may refer to an SRS triggered basedon higher layer signaling. An SRS trigger type 1 may refer to an SRStriggered based on one or more DCI formats. The wireless device may beconfigured to send/transmit an SRS, for example, after a transmission ofa PUSCH and a corresponding uplink DM-RS if a PUSCH and an SRS aresent/transmitted in a same slot. A base station may semi-staticallyconfigure a wireless device with one or more SRS configurationparameters indicating at least one of following: a SRS resourceconfiguration identifier; a number of SRS ports; time domain behavior ofan SRS resource configuration (e.g., an indication of periodic,semi-persistent, or aperiodic SRS); slot, mini-slot, and/or subframelevel periodicity; an offset for a periodic and/or an aperiodic SRSresource; a number of OFDM symbols in an SRS resource; a starting OFDMsymbol of an SRS resource; an SRS bandwidth; a frequency hoppingbandwidth; a cyclic shift; and/or an SRS sequence ID.

An antenna port may be determined/defined such that the channel overwhich a symbol on the antenna port is conveyed can be inferred from thechannel over which another symbol on the same antenna port is conveyed.The receiver may infer/determine the channel (e.g., fading gain,multipath delay, and/or the like) for conveying a second symbol on anantenna port, from the channel for conveying a first symbol on theantenna port, for example, if the first symbol and the second symbol aresent/transmitted on the same antenna port. A first antenna port and asecond antenna port may be referred to as quasi co-located (QCLed), forexample, if one or more large-scale properties of the channel over whicha first symbol on the first antenna port is conveyed may be inferredfrom the channel over which a second symbol on a second antenna port isconveyed. The one or more large-scale properties may comprise at leastone of: a delay spread; a Doppler spread; a Doppler shift; an averagegain; an average delay; and/or spatial Receiving (Rx) parameters.

Channels that use beamforming may require beam management. Beammanagement may comprise a beam measurement, a beam selection, and/or abeam indication. A beam may be associated with one or more referencesignals. A beam may be identified by one or more beamformed referencesignals. The wireless device may perform a downlink beam measurement,for example, based on one or more downlink reference signals (e.g., aCSI-RS) and generate a beam measurement report. The wireless device mayperform the downlink beam measurement procedure, for example, after anRRC connection is set up with a base station.

FIG. 11B shows an example mapping of one or more CSI-RSs. The CSI-RSsmay be mapped in the time and frequency domains. Each rectangular blockshown in FIG. 11B may correspond to a resource block (RB) within abandwidth of a cell. A base station may send/transmit one or more RRCmessages comprising CSI-RS resource configuration parameters indicatingone or more CSI-RSs. One or more of parameters may be configured byhigher layer signaling (e.g., RRC and/or MAC signaling) for a CSI-RSresource configuration. The one or more of the parameters may compriseat least one of: a CSI-RS resource configuration identity, a number ofCSI-RS ports, a CSI-RS configuration (e.g., symbol and resource element(RE) locations in a subframe), a CSI-RS subframe configuration (e.g., asubframe location, an offset, and periodicity in a radio frame), aCSI-RS power parameter, a CSI-RS sequence parameter, a code divisionmultiplexing (CDM) type parameter, a frequency density, a transmissioncomb, quasi co-location (QCL) parameters (e.g., QCL-scramblingidentity,crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid,qcl-csi-rs-configNZPid), and/or other radio resource parameters.

One or more beams may be configured for a wireless device in a wirelessdevice-specific configuration. Three beams are shown in FIG. 11B (beam#1, beam #2, and beam #3), but more or fewer beams may be configured.Beam #1 may be allocated with CSI-RS 1101 that may be sent/transmittedin one or more subcarriers in an RB of a first symbol. Beam #2 may beallocated with CSI-RS 1102 that may be sent/transmitted in one or moresubcarriers in an RB of a second symbol. Beam #3 may be allocated withCSI-RS 1103 that may be sent/transmitted in one or more subcarriers inan RB of a third symbol. A base station may use other subcarriers in thesame RB (e.g., those that are not used to send/transmit CSI-RS 1101) totransmit another CSI-RS associated with a beam for another wirelessdevice, for example, by using frequency division multiplexing (FDM).Beams used for a wireless device may be configured such that beams forthe wireless device use symbols different from symbols used by beams ofother wireless devices, for example, by using time domain multiplexing(TDM). A wireless device may be served with beams in orthogonal symbols(e.g., no overlapping symbols), for example, by using the TDM.

CSI-RSs (e.g., CSI-RSs 1101, 1102, 1103) may be sent/transmitted by thebase station and used by the wireless device for one or moremeasurements. The wireless device may measure an RSRP of configuredCSI-RS resources. The base station may configure the wireless devicewith a reporting configuration, and the wireless device may report theRSRP measurements to a network (e.g., via one or more base stations)based on the reporting configuration. The base station may determine,based on the reported measurement results, one or more transmissionconfiguration indication (TCI) states comprising a number of referencesignals. The base station may indicate one or more TCI states to thewireless device (e.g., via RRC signaling, a MAC CE, and/or DCI). Thewireless device may receive a downlink transmission with an Rx beamdetermined based on the one or more TCI states. The wireless device mayor may not have a capability of beam correspondence. The wireless devicemay determine a spatial domain filter of a transmit (Tx) beam, forexample, based on a spatial domain filter of the corresponding Rx beam,if the wireless device has the capability of beam correspondence. Thewireless device may perform an uplink beam selection procedure todetermine the spatial domain filter of the Tx beam, for example, if thewireless device does not have the capability of beam correspondence. Thewireless device may perform the uplink beam selection procedure, forexample, based on one or more sounding reference signal (SRS) resourcesconfigured to the wireless device by the base station. The base stationmay select and indicate uplink beams for the wireless device, forexample, based on measurements of the one or more SRS resourcessent/transmitted by the wireless device.

A wireless device may determine/assess (e.g., measure) a channel qualityof one or more beam pair links, for example, in a beam managementprocedure. A beam pair link may comprise a Tx beam of a base station andan Rx beam of the wireless device. The Tx beam of the base station maysend/transmit a downlink signal, and the Rx beam of the wireless devicemay receive the downlink signal. The wireless device may send/transmit abeam measurement report, for example, based on theassessment/determination. The beam measurement report may indicate oneor more beam pair quality parameters comprising at least one of: one ormore beam identifications (e.g., a beam index, a reference signal index,or the like), an RSRP, a precoding matrix indicator (PMI), a channelquality indicator (CQI), and/or a rank indicator (RI).

FIG. 12A shows examples of downlink beam management procedures. One ormore downlink beam management procedures (e.g., downlink beam managementprocedures P1, P2, and P3) may be performed. Procedure P1 may enable ameasurement (e.g., a wireless device measurement) on Tx beams of a TRP(or multiple TRPs) (e.g., to support a selection of one or more basestation Tx beams and/or wireless device Rx beams). The Tx beams of abase station and the Rx beams of a wireless device are shown as ovals inthe top row of P1 and bottom row of P1, respectively. Beamforming (e.g.,at a TRP) may comprise a Tx beam sweep for a set of beams (e.g., thebeam sweeps shown, in the top rows of P1 and P2, as ovals rotated in acounter-clockwise direction indicated by the dashed arrows). Beamforming(e.g., at a wireless device) may comprise an Rx beam sweep for a set ofbeams (e.g., the beam sweeps shown, in the bottom rows of P1 and P3, asovals rotated in a clockwise direction indicated by the dashed arrows).Procedure P2 may be used to enable a measurement (e.g., a wirelessdevice measurement) on Tx beams of a TRP (shown, in the top row of P2,as ovals rotated in a counter-clockwise direction indicated by thedashed arrow). The wireless device and/or the base station may performprocedure P2, for example, using a smaller set of beams than the set ofbeams used in procedure P1, or using narrower beams than the beams usedin procedure P1. Procedure P2 may be referred to as a beam refinement.The wireless device may perform procedure P3 for an Rx beamdetermination, for example, by using the same Tx beam(s) of the basestation and sweeping Rx beam(s) of the wireless device.

FIG. 12B shows examples of uplink beam management procedures. One ormore uplink beam management procedures (e.g., uplink beam managementprocedures U1, U2, and U3) may be performed. Procedure U1 may be used toenable a base station to perform a measurement on Tx beams of a wirelessdevice (e.g., to support a selection of one or more Tx beams of thewireless device and/or Rx beams of the base station). The Tx beams ofthe wireless device and the Rx beams of the base station are shown asovals in the top row of U1 and bottom row of U1, respectively).Beamforming (e.g., at the wireless device) may comprise one or more beamsweeps, for example, a Tx beam sweep from a set of beams (shown, in thebottom rows of U1 and U3, as ovals rotated in a clockwise directionindicated by the dashed arrows). Beamforming (e.g., at the base station)may comprise one or more beam sweeps, for example, an Rx beam sweep froma set of beams (shown, in the top rows of U1 and U2, as ovals rotated ina counter-clockwise direction indicated by the dashed arrows). ProcedureU2 may be used to enable the base station to adjust its Rx beam, forexample, if the UE uses a fixed Tx beam. The wireless device and/or thebase station may perform procedure U2, for example, using a smaller setof beams than the set of beams used in procedure P1, or using narrowerbeams than the beams used in procedure P1. Procedure U2 may be referredto as a beam refinement. The wireless device may perform procedure U3 toadjust its Tx beam, for example, if the base station uses a fixed Rxbeam.

A wireless device may initiate/start/perform a beam failure recovery(BFR) procedure, for example, based on detecting a beam failure. Thewireless device may send/transmit a BFR request (e.g., a preamble, UCI,an SR, a MAC CE, and/or the like), for example, based on the initiatingthe BFR procedure. The wireless device may detect the beam failure, forexample, based on a determination that a quality of beam pair link(s) ofan associated control channel is unsatisfactory (e.g., having an errorrate higher than an error rate threshold, a received signal power lowerthan a received signal power threshold, an expiration of a timer, and/orthe like).

The wireless device may measure a quality of a beam pair link, forexample, using one or more reference signals (RSs) comprising one ormore SS/PBCH blocks, one or more CSI-RS resources, and/or one or moreDM-RSs. A quality of the beam pair link may be based on one or more of ablock error rate (BLER), an RSRP value, a signal to interference plusnoise ratio (SINR) value, an RSRQ value, and/or a CSI value measured onRS resources. The base station may indicate that an RS resource is QCLedwith one or more DM-RSs of a channel (e.g., a control channel, a shareddata channel, and/or the like). The RS resource and the one or moreDM-RSs of the channel may be QCLed, for example, if the channelcharacteristics (e.g., Doppler shift, Doppler spread, an average delay,delay spread, a spatial Rx parameter, fading, and/or the like) from atransmission via the RS resource to the wireless device are similar orthe same as the channel characteristics from a transmission via thechannel to the wireless device.

A network (e.g., an NR network comprising a gNB and/or an ng-eNB) and/orthe wireless device may initiate/start/perform a random accessprocedure. A wireless device in an RRC idle (e.g., an RRC_IDLE) stateand/or an RRC inactive (e.g., an RRC_INACTIVE) state mayinitiate/perform the random access procedure to request a connectionsetup to a network. The wireless device may initiate/start/perform therandom access procedure from an RRC connected (e.g., an RRC_CONNECTED)state. The wireless device may initiate/start/perform the random accessprocedure to request uplink resources (e.g., for uplink transmission ofan SR if there is no PUCCH resource available) and/oracquire/obtain/determine an uplink timing (e.g., if an uplinksynchronization status is non-synchronized). The wireless device mayinitiate/start/perform the random access procedure to request one ormore system information blocks (SIBs) (e.g., other system informationblocks, such as SIB2, SIB3, and/or the like). The wireless device mayinitiate/start/perform the random access procedure for a beam failurerecovery request. A network may initiate/start/perform a random accessprocedure, for example, for a handover and/or for establishing timealignment for an SCell addition.

FIG. 13A shows an example four-step random access procedure. Thefour-step random access procedure may comprise a four-stepcontention-based random access procedure. A base station maysend/transmit a configuration message 1310 to a wireless device, forexample, before initiating the random access procedure. The four-steprandom access procedure may comprise transmissions of four messagescomprising: a first message (e.g., Msg 1 1311), a second message (e.g.,Msg 2 1312), a third message (e.g., Msg 3 1313), and a fourth message(e.g., Msg 4 1314). The first message (e.g., Msg 1 1311) may comprise apreamble (or a random access preamble). The first message (e.g., Msg 11311) may be referred to as a preamble. The second message (e.g., Msg 21312) may comprise as a random access response (RAR). The second message(e.g., Msg 2 1312) may be referred to as an RAR.

The configuration message 1310 may be sent/transmitted, for example,using one or more RRC messages. The one or more RRC messages mayindicate one or more random access channel (RACH) parameters to thewireless device. The one or more RACH parameters may comprise at leastone of: general parameters for one or more random access procedures(e.g., RACH-configGeneral); cell-specific parameters (e.g.,RACH-ConfigCommon); and/or dedicated parameters (e.g.,RACH-configDedicated). The base station may send/transmit (e.g.,broadcast or multicast) the one or more RRC messages to one or morewireless devices. The one or more RRC messages may be wirelessdevice-specific. The one or more RRC messages that are wirelessdevice-specific may be, for example, dedicated RRC messagessent/transmitted to a wireless device in an RRC connected (e.g., anRRC_CONNECTED) state and/or in an RRC inactive (e.g., an RRC_INACTIVE)state. The wireless devices may determine, based on the one or more RACHparameters, a time-frequency resource and/or an uplink transmit powerfor transmission of the first message (e.g., Msg 1 1311) and/or thethird message (e.g., Msg 3 1313). The wireless device may determine areception timing and a downlink channel for receiving the second message(e.g., Msg 2 1312) and the fourth message (e.g., Msg 4 1314), forexample, based on the one or more RACH parameters.

The one or more RACH parameters provided/configured/comprised in theconfiguration message 1310 may indicate one or more Physical RACH(PRACH) occasions available for transmission of the first message (e.g.,Msg 1 1311). The one or more PRACH occasions may be predefined (e.g., bya network comprising one or more base stations). The one or more RACHparameters may indicate one or more available sets of one or more PRACHoccasions (e.g., prach-ConfigIndex). The one or more RACH parameters mayindicate an association between (a) one or more PRACH occasions and (b)one or more reference signals. The one or more RACH parameters mayindicate an association between (a) one or more preambles and (b) one ormore reference signals. The one or more reference signals may be SS/PBCHblocks and/or CSI-RSs. The one or more RACH parameters may indicate aquantity/number of SS/PBCH blocks mapped to a PRACH occasion and/or aquantity/number of preambles mapped to a SS/PBCH blocks.

The one or more RACH parameters provided/configured/comprised in theconfiguration message 1310 may be used to determine an uplink transmitpower of first message (e.g., Msg 1 1311) and/or third message (e.g.,Msg 3 1313). The one or more RACH parameters may indicate a referencepower for a preamble transmission (e.g., a received target power and/oran initial power of the preamble transmission). There may be one or morepower offsets indicated by the one or more RACH parameters. The one ormore RACH parameters may indicate: a power ramping step; a power offsetbetween SSB and CSI-RS; a power offset between transmissions of thefirst message (e.g., Msg 1 1311) and the third message (e.g., Msg 31313); and/or a power offset value between preamble groups. The one ormore RACH parameters may indicate one or more thresholds, for example,based on which the wireless device may determine at least one referencesignal (e.g., an SSB and/or CSI-RS) and/or an uplink carrier (e.g., anormal uplink (NUL) carrier and/or a supplemental uplink (SUL) carrier).

The first message (e.g., Msg 1 1311) may comprise one or more preambletransmissions (e.g., a preamble transmission and one or more preambleretransmissions). An RRC message may be used to configure one or morepreamble groups (e.g., group A and/or group B). A preamble group maycomprise one or more preambles. The wireless device may determine thepreamble group, for example, based on a pathloss measurement and/or asize of the third message (e.g., Msg 3 1313). The wireless device maymeasure an RSRP of one or more reference signals (e.g., SSBs and/orCSI-RSs) and determine at least one reference signal having an RSRPabove an RSRP threshold (e.g., rsrp-ThresholdSSB and/orrsrp-ThresholdCSI-RS). The wireless device may select at least onepreamble associated with the one or more reference signals and/or aselected preamble group, for example, if the association between the oneor more preambles and the at least one reference signal is configured byan RRC message.

The wireless device may determine the preamble, for example, based onthe one or more RACH parameters provided/configured/comprised in theconfiguration message 1310. The wireless device may determine thepreamble, for example, based on a pathloss measurement, an RSRPmeasurement, and/or a size of the third message (e.g., Msg 3 1313). Theone or more RACH parameters may indicate: a preamble format; a maximumquantity/number of preamble transmissions; and/or one or more thresholdsfor determining one or more preamble groups (e.g., group A and group B).A base station may use the one or more RACH parameters to configure thewireless device with an association between one or more preambles andone or more reference signals (e.g., SSBs and/or CSI-RSs). The wirelessdevice may determine the preamble to be comprised in first message(e.g., Msg 1 1311), for example, based on the association if theassociation is configured. The first message (e.g., Msg 1 1311) may besent/transmitted to the base station via one or more PRACH occasions.The wireless device may use one or more reference signals (e.g., SSBsand/or CSI-RSs) for selection of the preamble and for determining of thePRACH occasion. One or more RACH parameters (e.g.,ra-ssb-OccasionMskIndex and/or ra-OccasionList) may indicate anassociation between the PRACH occasions and the one or more referencesignals.

The wireless device may perform a preamble retransmission, for example,if no response is received after (e.g., based on or in response to) apreamble transmission (e.g., for a period of time, such as a monitoringwindow for monitoring an RAR). The wireless device may increase anuplink transmit power for the preamble retransmission. The wirelessdevice may select an initial preamble transmit power, for example, basedon a pathloss measurement and/or a target received preamble powerconfigured by the network. The wireless device may determine toresend/retransmit a preamble and may ramp up the uplink transmit power.The wireless device may receive one or more RACH parameters (e.g.,PREAMBLE_POWER_RAMPING_STEP) indicating a ramping step for the preambleretransmission. The ramping step may be an amount of incrementalincrease in uplink transmit power for a retransmission. The wirelessdevice may ramp up the uplink transmit power, for example, if thewireless device determines a reference signal (e.g., SSB and/or CSI-RS)that is the same as a previous preamble transmission. The wirelessdevice may count the quantity/number of preamble transmissions and/orretransmissions, for example, using a counter parameter (e.g.,PREAMBLE_TRANSMISSION_COUNTER). The wireless device may determine that arandom access procedure has been completed unsuccessfully, for example,if the quantity/number of preamble transmissions exceeds a thresholdconfigured by the one or more RACH parameters (e.g., preambleTransMax)without receiving a successful response (e.g., an RAR).

The second message (e.g., Msg 2 1312) (e.g., received by the wirelessdevice) may comprise an RAR. The second message (e.g., Msg 2 1312) maycomprise multiple RARs corresponding to multiple wireless devices. Thesecond message (e.g., Msg 2 1312) may be received, for example, after(e.g., based on or in response to) the sending/transmitting of the firstmessage (e.g., Msg 1 1311). The second message (e.g., Msg 2 1312) may bescheduled on the DL-SCH and may be indicated by a PDCCH, for example,using a random access radio network temporary identifier (RA RNTI). Thesecond message (e.g., Msg 2 1312) may indicate that the first message(e.g., Msg 1 1311) was received by the base station. The second message(e.g., Msg 2 1312) may comprise a time-alignment command that may beused by the wireless device to adjust the transmission timing of thewireless device, a scheduling grant for transmission of the thirdmessage (e.g., Msg 3 1313), and/or a Temporary Cell RNTI (TC-RNTI). Thewireless device may determine/start a time window (e.g.,ra-ResponseWindow) to monitor a PDCCH for the second message (e.g., Msg2 1312), for example, after sending/transmitting the first message(e.g., Msg 1 1311) (e.g., a preamble). The wireless device may determinethe start time of the time window, for example, based on a PRACHoccasion that the wireless device uses to send/transmit the firstmessage (e.g., Msg 1 1311) (e.g., the preamble). The wireless device maystart the time window one or more symbols after the last symbol of thefirst message (e.g., Msg 1 1311) comprising the preamble (e.g., thesymbol in which the first message (e.g., Msg 1 1311) comprising thepreamble transmission was completed or at a first PDCCH occasion from anend of a preamble transmission). The one or more symbols may bedetermined based on a numerology. The PDCCH may be mapped in a commonsearch space (e.g., a Type1-PDCCH common search space) configured by anRRC message. The wireless device may identify/determine the RAR, forexample, based on an RNTI. Radio network temporary identifiers (RNTIs)may be used depending on one or more events initiating/starting therandom access procedure. The wireless device may use a RA-RNTI, forexample, for one or more communications associated with random access orany other purpose. The RA-RNTI may be associated with PRACH occasions inwhich the wireless device sends/transmits a preamble. The wirelessdevice may determine the RA-RNTI, for example, based on at least one of:an OFDM symbol index; a slot index; a frequency domain index; and/or aUL carrier indicator of the PRACH occasions. An example RA-RNTI may bedetermined as follows:RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_idwhere s_id may be an index of a first OFDM symbol of the PRACH occasion(e.g., 0≤s_id≤14), t_id may be an index of a first slot of the PRACHoccasion in a system frame (e.g., 0≤t_id≤80), f_id may be an index ofthe PRACH occasion in the frequency domain (e.g., 0≤f_id≤8), andul_carrier_id may be a UL carrier used for a preamble transmission(e.g., 0 for an NUL carrier, and 1 for an SUL carrier).

The wireless device may send/transmit the third message (e.g., Msg 31313), for example, after (e.g., based on or in response to) asuccessful reception of the second message (e.g., Msg 2 1312) (e.g.,using resources identified in the Msg 2 1312). The third message (e.g.,Msg 3 1313) may be used, for example, for contention resolution in thecontention-based random access procedure. A plurality of wirelessdevices may send/transmit the same preamble to a base station, and thebase station may send/transmit an RAR that corresponds to a wirelessdevice. Collisions may occur, for example, if the plurality of wirelessdevice interpret the RAR as corresponding to themselves. Contentionresolution (e.g., using the third message (e.g., Msg 3 1313) and thefourth message (e.g., Msg 4 1314)) may be used to increase thelikelihood that the wireless device does not incorrectly use an identityof another the wireless device. The wireless device may comprise adevice identifier in the third message (e.g., Msg 3 1313) (e.g., aC-RNTI if assigned, a TC RNTI comprised in the second message (e.g., Msg2 1312), and/or any other suitable identifier), for example, to performcontention resolution.

The fourth message (e.g., Msg 4 1314) may be received, for example,after (e.g., based on or in response to) the sending/transmitting of thethird message (e.g., Msg 3 1313). The base station may address thewireless device on the PDCCH (e.g., the base station may send the PDCCHto the wireless device) using a C-RNTI, for example, if the C-RNTI wasincluded in the third message (e.g., Msg 3 1313). The random accessprocedure may be determined to be successfully completed, for example,if the unique C RNTI of the wireless device is detected on the PDCCH(e.g., the PDCCH is scrambled by the C-RNTI). Fourth message (e.g., Msg4 1314) may be received using a DL-SCH associated with a TC RNTI, forexample, if the TC RNTI is comprised in the third message (e.g., Msg 31313) (e.g., if the wireless device is in an RRC idle (e.g., anRRC_IDLE) state or not otherwise connected to the base station). Thewireless device may determine that the contention resolution issuccessful and/or the wireless device may determine that the randomaccess procedure is successfully completed, for example, if a MAC PDU issuccessfully decoded and a MAC PDU comprises the wireless devicecontention resolution identity MAC CE that matches or otherwisecorresponds with the CCCH SDU sent/transmitted in third message (e.g.,Msg 3 1313).

The wireless device may be configured with an SUL carrier and/or an NULcarrier. An initial access (e.g., random access) may be supported via anuplink carrier. A base station may configure the wireless device withmultiple RACH configurations (e.g., two separate RACH configurationscomprising: one for an SUL carrier and the other for an NUL carrier).For random access in a cell configured with an SUL carrier, the networkmay indicate which carrier to use (NUL or SUL). The wireless device maydetermine to use the SUL carrier, for example, if a measured quality ofone or more reference signals (e.g., one or more reference signalsassociated with the NUL carrier) is lower than a broadcast threshold.Uplink transmissions of the random access procedure (e.g., the firstmessage (e.g., Msg 1 1311) and/or the third message (e.g., Msg 3 1313))may remain on, or may be performed via, the selected carrier. Thewireless device may switch an uplink carrier during the random accessprocedure (e.g., between the Msg 1 1311 and the Msg 3 1313). Thewireless device may determine and/or switch an uplink carrier for thefirst message (e.g., Msg 1 1311) and/or the third message (e.g., Msg 31313), for example, based on a channel clear assessment (e.g., alisten-before-talk).

FIG. 13B shows a two-step random access procedure. The two-step randomaccess procedure may comprise a two-step contention-free random accessprocedure. Similar to the four-step contention-based random accessprocedure, a base station may, prior to initiation of the procedure,send/transmit a configuration message 1320 to the wireless device. Theconfiguration message 1320 may be analogous in some respects to theconfiguration message 1310. The procedure shown in FIG. 13B may comprisetransmissions of two messages: a first message (e.g., Msg 1 1321) and asecond message (e.g., Msg 2 1322). The first message (e.g., Msg 1 1321)and the second message (e.g., Msg 2 1322) may be analogous in somerespects to the first message (e.g., Msg 1 1311) and a second message(e.g., Msg 2 1312), respectively. The two-step contention-free randomaccess procedure may not comprise messages analogous to the thirdmessage (e.g., Msg 3 1313) and/or the fourth message (e.g., Msg 4 1314).

The two-step (e.g., contention-free) random access procedure may beconfigured/initiated for a beam failure recovery, other SI request, anSCell addition, and/or a handover. A base station may indicate, orassign to, the wireless device a preamble to be used for the firstmessage (e.g., Msg 1 1321). The wireless device may receive, from thebase station via a PDCCH and/or an RRC, an indication of the preamble(e.g., ra-PreambleIndex).

The wireless device may start a time window (e.g., ra-ResponseWindow) tomonitor a PDCCH for the RAR, for example, after (e.g., based on or inresponse to) sending/transmitting the preamble. The base station mayconfigure the wireless device with one or more beam failure recoveryparameters, such as a separate time window and/or a separate PDCCH in asearch space indicated by an RRC message (e.g., recoverySearchSpaceId).The base station may configure the one or more beam failure recoveryparameters, for example, in association with a beam failure recoveryrequest. The separate time window for monitoring the PDCCH and/or an RARmay be configured to start after sending/transmitting a beam failurerecovery request (e.g., the window may start any quantity of symbolsand/or slots after transmitting the beam failure recovery request). Thewireless device may monitor for a PDCCH transmission addressed to a CellRNTI (C-RNTI) on the search space. During the two-step (e.g.,contention-free) random access procedure, the wireless device maydetermine that a random access procedure is successful, for example,after (e.g., based on or in response to) transmitting first message(e.g., Msg 1 1321) and receiving a corresponding second message (e.g.,Msg 2 1322). The wireless device may determine that a random accessprocedure has successfully been completed, for example, if a PDCCHtransmission is addressed to a corresponding C-RNTI. The wireless devicemay determine that a random access procedure has successfully beencompleted, for example, if the wireless device receives an RARcomprising a preamble identifier corresponding to a preamblesent/transmitted by the wireless device and/or the RAR comprises a MACsub-PDU with the preamble identifier. The wireless device may determinethe response as an indication of an acknowledgement for an SI request.

FIG. 13C shows an example two-step random access procedure. Similar tothe random access procedures shown in FIGS. 13A and 13B, a base stationmay, prior to initiation of the procedure, send/transmit a configurationmessage 1330 to the wireless device. The configuration message 1330 maybe analogous in some respects to the configuration message 1310 and/orthe configuration message 1320. The procedure shown in FIG. 13C maycomprise transmissions of multiple messages (e.g., two messagescomprising: a first message (e.g., Msg A 1331) and a second message(e.g., Msg B 1332)).

Msg A 1320 may be sent/transmitted in an uplink transmission by thewireless device. Msg A 1320 may comprise one or more transmissions of apreamble 1341 and/or one or more transmissions of a transport block1342. The transport block 1342 may comprise contents that are similarand/or equivalent to the contents of the third message (e.g., Msg 31313) (e.g., shown in FIG. 13A). The transport block 1342 may compriseUCI (e.g., an SR, a HARQ ACK/NACK, and/or the like). The wireless devicemay receive the second message (e.g., Msg B 1332), for example, after(e.g., based on or in response to) sending/transmitting the firstmessage (e.g., Msg A 1331). The second message (e.g., Msg B 1332) maycomprise contents that are similar and/or equivalent to the contents ofthe second message (e.g., Msg 2 1312) (e.g., an RAR shown in FIGS. 13A),the contents of the second message (e.g., Msg 2 1322) (e.g., an RARshown in FIG. 13B) and/or the fourth message (e.g., Msg 4 1314) (e.g.,shown in FIG. 13A).

The wireless device may start/initiate the two-step random accessprocedure (e.g., the two-step random access procedure shown in FIG. 13C)for a licensed spectrum and/or an unlicensed spectrum. The wirelessdevice may determine, based on one or more factors, whether tostart/initiate the two-step random access procedure. The one or morefactors may comprise at least one of: a radio access technology in use(e.g., LTE, NR, and/or the like); whether the wireless device has avalid TA or not; a cell size; the RRC state of the wireless device; atype of spectrum (e.g., licensed vs. unlicensed); and/or any othersuitable factors.

The wireless device may determine, based on two-step RACH parameterscomprised in the configuration message 1330, a radio resource and/or anuplink transmit power for the preamble 1341 and/or the transport block1342 (e.g., comprised in the first message (e.g., Msg A 1331)). The RACHparameters may indicate an MCS, a time-frequency resource, and/or apower control for the preamble 1341 and/or the transport block 1342. Atime-frequency resource for transmission of the preamble 1341 (e.g., aPRACH) and a time-frequency resource for transmission of the transportblock 1342 (e.g., a PUSCH) may be multiplexed using FDM, TDM, and/orCDM. The RACH parameters may enable the wireless device to determine areception timing and a downlink channel for monitoring for and/orreceiving second message (e.g., Msg B 1332).

The transport block 1342 may comprise data (e.g., delay-sensitive data),an identifier of the wireless device, security information, and/ordevice information (e.g., an International Mobile Subscriber Identity(IMSI)). The base station may send/transmit the second message (e.g.,Msg B 1332) as a response to the first message (e.g., Msg A 1331). Thesecond message (e.g., Msg B 1332) may comprise at least one of: apreamble identifier; a timing advance command; a power control command;an uplink grant (e.g., a radio resource assignment and/or an MCS); awireless device identifier (e.g., a UE identifier for contentionresolution); and/or an RNTI (e.g., a C-RNTI or a TC-RNTI). The wirelessdevice may determine that the two-step random access procedure issuccessfully completed, for example, if a preamble identifier in thesecond message (e.g., Msg B 1332) corresponds to, or is matched to, apreamble sent/transmitted by the wireless device and/or the identifierof the wireless device in second message (e.g., Msg B 1332) correspondsto, or is matched to, the identifier of the wireless device in the firstmessage (e.g., Msg A 1331) (e.g., the transport block 1342).

A wireless device and a base station may exchange control signaling(e.g., control information). The control signaling may be referred to asL1/L2 control signaling and may originate from the PHY layer (e.g.,layer 1) and/or the MAC layer (e.g., layer 2) of the wireless device orthe base station. The control signaling may comprise downlink controlsignaling sent/transmitted from the base station to the wireless deviceand/or uplink control signaling sent/transmitted from the wirelessdevice to the base station.

The downlink control signaling may comprise at least one of: a downlinkscheduling assignment; an uplink scheduling grant indicating uplinkradio resources and/or a transport format; slot format information; apreemption indication; a power control command; and/or any othersuitable signaling. The wireless device may receive the downlink controlsignaling in a payload sent/transmitted by the base station via a PDCCH.The payload sent/transmitted via the PDCCH may be referred to asdownlink control information (DCI). The PDCCH may be a group commonPDCCH (GC-PDCCH) that is common to a group of wireless devices. TheGC-PDCCH may be scrambled by a group common RNTI.

A base station may attach one or more cyclic redundancy check (CRC)parity bits to DCI, for example, in order to facilitate detection oftransmission errors. The base station may scramble the CRC parity bitswith an identifier of a wireless device (or an identifier of a group ofwireless devices), for example, if the DCI is intended for the wirelessdevice (or the group of the wireless devices). Scrambling the CRC paritybits with the identifier may comprise Modulo-2 addition (or anexclusive-OR operation) of the identifier value and the CRC parity bits.The identifier may comprise a 16-bit value of an RNTI.

DCIs may be used for different purposes. A purpose may be indicated bythe type of an RNTI used to scramble the CRC parity bits. DCI having CRCparity bits scrambled with a paging RNTI (P-RNTI) may indicate paginginformation and/or a system information change notification. The P-RNTImay be predefined as “FFFE” in hexadecimal. DCI having CRC parity bitsscrambled with a system information RNTI (SI-RNTI) may indicate abroadcast transmission of the system information. The SI-RNTI may bepredefined as “FFFF” in hexadecimal. DCI having CRC parity bitsscrambled with a random access RNTI (RA-RNTI) may indicate a randomaccess response (RAR). DCI having CRC parity bits scrambled with a cellRNTI (C-RNTI) may indicate a dynamically scheduled unicast transmissionand/or a triggering of PDCCH-ordered random access. DCI having CRCparity bits scrambled with a temporary cell RNTI (TC-RNTI) may indicatea contention resolution (e.g., a Msg 3 analogous to the Msg 3 1313 shownin FIG. 13A). Other RNTIs configured for a wireless device by a basestation may comprise a Configured Scheduling RNTI (CS RNTI), a TransmitPower Control-PUCCH RNTI (TPC PUCCH-RNTI), a Transmit PowerControl-PUSCH RNTI (TPC-PUSCH-RNTI), a Transmit Power Control-SRS RNTI(TPC-SRS-RNTI), an Interruption RNTI (INT-RNTI), a Slot FormatIndication RNTI (SFI-RNTI), a Semi-Persistent CSI RNTI (SP-CSI-RNTI), aModulation and Coding Scheme Cell RNTI (MCS-C RNTI), and/or the like.

A base station may send/transmit DCIs with one or more DCI formats, forexample, depending on the purpose and/or content of the DCIs. DCI format0_0 may be used for scheduling of a PUSCH in a cell. DCI format 0_0 maybe a fallback DCI format (e.g., with compact DCI payloads). DCI format0_1 may be used for scheduling of a PUSCH in a cell (e.g., with more DCIpayloads than DCI format 0_0). DCI format 10 may be used for schedulingof a PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g.,with compact DCI payloads). DCI format 1_1 may be used for scheduling ofa PDSCH in a cell (e.g., with more DCI payloads than DCI format 1_0).DCI format 2_0 may be used for providing a slot format indication to agroup of wireless devices. DCI format 2_1 may be used forinforming/notifying a group of wireless devices of a physical resourceblock and/or an OFDM symbol where the group of wireless devices mayassume no transmission is intended to the group of wireless devices. DCIformat 22 may be used for transmission of a transmit power control (TPC)command for PUCCH or PUSCH. DCI format 2_3 may be used for transmissionof a group of TPC commands for SRS transmissions by one or more wirelessdevices. DCI format(s) for new functions may be defined in futurereleases. DCI formats may have different DCI sizes, or may share thesame DCI size.

The base station may process the DCI with channel coding (e.g., polarcoding), rate matching, scrambling and/or QPSK modulation, for example,after scrambling the DCI with an RNTI. A base station may map the codedand modulated DCI on resource elements used and/or configured for aPDCCH. The base station may send/transmit the DCI via a PDCCH occupyinga number of contiguous control channel elements (CCEs), for example,based on a payload size of the DCI and/or a coverage of the basestation. The number of the contiguous CCEs (referred to as aggregationlevel) may be 1, 2, 4, 8, 16, and/or any other suitable number. A CCEmay comprise a number (e.g., 6) of resource-element groups (REGs). A REGmay comprise a resource block in an OFDM symbol. The mapping of thecoded and modulated DCI on the resource elements may be based on mappingof CCEs and REGs (e.g., CCE-to-REG mapping).

FIG. 14A shows an example of CORESET configurations. The CORESETconfigurations may be for a bandwidth part or any other frequency bands.The base station may send/transmit DCI via a PDCCH on one or morecontrol resource sets (CORESETs). A CORESET may comprise atime-frequency resource in which the wireless device attempts/tries todecode DCI using one or more search spaces. The base station mayconfigure a size and a location of the CORESET in the time-frequencydomain. A first CORESET 1401 and a second CORESET 1402 may occur or maybe set/configured at the first symbol in a slot. The first CORESET 1401may overlap with the second CORESET 1402 in the frequency domain. Athird CORESET 1403 may occur or may be set/configured at a third symbolin the slot. A fourth CORESET 1404 may occur or may be set/configured atthe seventh symbol in the slot. CORESETs may have a different number ofresource blocks in frequency domain.

FIG. 14B shows an example of a CCE-to-REG mapping. The CCE-to-REGmapping may be performed for DCI transmission via a CORESET and PDCCHprocessing. The CCE-to-REG mapping may be an interleaved mapping (e.g.,for the purpose of providing frequency diversity) or a non-interleavedmapping (e.g., for the purposes of facilitating interferencecoordination and/or frequency-selective transmission of controlchannels). The base station may perform different or same CCE-to-REGmapping on different CORESETs. A CORESET may be associated with aCCE-to-REG mapping (e.g., by an RRC configuration). A CORESET may beconfigured with an antenna port QCL parameter. The antenna port QCLparameter may indicate QCL information of a DM-RS for a PDCCH receptionvia the CORESET.

The base station may send/transmit, to the wireless device, one or moreRRC messages comprising configuration parameters of one or more CORESETsand one or more search space sets. The configuration parameters mayindicate an association between a search space set and a CORESET. Asearch space set may comprise a set of PDCCH candidates formed by CCEs(e.g., at a given aggregation level). The configuration parameters mayindicate at least one of: a number of PDCCH candidates to be monitoredper aggregation level; a PDCCH monitoring periodicity and a PDCCHmonitoring pattern; one or more DCI formats to be monitored by thewireless device; and/or whether a search space set is a common searchspace set or a wireless device-specific search space set (e.g., aUE-specific search space set). A set of CCEs in the common search spaceset may be predefined and known to the wireless device. A set of CCEs inthe wireless device-specific search space set (e.g., the UE-specificsearch space set) may be configured, for example, based on the identityof the wireless device (e.g., C-RNTI).

As shown in FIG. 14B, the wireless device may determine a time-frequencyresource for a CORESET based on one or more RRC messages. The wirelessdevice may determine a CCE-to-REG mapping (e.g., interleaved ornon-interleaved, and/or mapping parameters) for the CORESET, forexample, based on configuration parameters of the CORESET. The wirelessdevice may determine a number (e.g., at most 10) of search space setsconfigured on/for the CORESET, for example, based on the one or more RRCmessages. The wireless device may monitor a set of PDCCH candidatesaccording to configuration parameters of a search space set. Thewireless device may monitor a set of PDCCH candidates in one or moreCORESETs for detecting one or more DCIs. Monitoring may comprisedecoding one or more PDCCH candidates of the set of the PDCCH candidatesaccording to the monitored DCI formats. Monitoring may comprise decodingDCI content of one or more PDCCH candidates with possible (orconfigured) PDCCH locations, possible (or configured) PDCCH formats(e.g., the number of CCEs, the number of PDCCH candidates in commonsearch spaces, and/or the number of PDCCH candidates in the wirelessdevice-specific search spaces) and possible (or configured) DCI formats.The decoding may be referred to as blind decoding. The wireless devicemay determine DCI as valid for the wireless device, for example, after(e.g., based on or in response to) CRC checking (e.g., scrambled bitsfor CRC parity bits of the DCI matching an RNTI value). The wirelessdevice may process information comprised in the DCI (e.g., a schedulingassignment, an uplink grant, power control, a slot format indication, adownlink preemption, and/or the like).

The wireless device may send/transmit uplink control signaling (e.g.,UCI) to a base station. The uplink control signaling may comprise HARQacknowledgements for received DL-SCH transport blocks. The wirelessdevice may send/transmit the HARQ acknowledgements, for example, after(e.g., based on or in response to) receiving a DL-SCH transport block.Uplink control signaling may comprise CSI indicating a channel qualityof a physical downlink channel. The wireless device may send/transmitthe CSI to the base station. The base station, based on the receivedCSI, may determine transmission format parameters (e.g., comprisingmulti-antenna and beamforming schemes) for downlink transmission(s).Uplink control signaling may comprise scheduling requests (SR). Thewireless device may send/transmit an SR indicating that uplink data isavailable for transmission to the base station. The wireless device maysend/transmit UCI (e.g., HARQ acknowledgements (HARQ-ACK), CSI report,SR, and the like) via a PUCCH or a PUSCH. The wireless device maysend/transmit the uplink control signaling via a PUCCH using one ofseveral PUCCH formats.

There may be multiple PUCCH formats (e.g., five PUCCH formats). Awireless device may determine a PUCCH format, for example, based on asize of UCI (e.g., a quantity/number of uplink symbols of UCItransmission and a number of UCI bits). PUCCH format 0 may have a lengthof one or two OFDM symbols and may comprise two or fewer bits. Thewireless device may send/transmit UCI via a PUCCH resource, for example,using PUCCH format 0 if the transmission is over/via one or two symbolsand the quantity/number of HARQ-ACK information bits with positive ornegative SR (HARQ-ACK/SR bits) is one or two. PUCCH format 1 may occupya number of OFDM symbols (e.g., between four and fourteen OFDM symbols)and may comprise two or fewer bits. The wireless device may use PUCCHformat 1, for example, if the transmission is over/via four or moresymbols and the number of HARQ-ACK/SR bits is one or two. PUCCH format 2may occupy one or two OFDM symbols and may comprise more than two bits.The wireless device may use PUCCH format 2, for example, if thetransmission is over/via one or two symbols and the quantity/number ofUCI bits is two or more. PUCCH format 3 may occupy a number of OFDMsymbols (e.g., between four and fourteen OFDM symbols) and may comprisemore than two bits. The wireless device may use PUCCH format 3, forexample, if the transmission is four or more symbols, thequantity/number of UCI bits is two or more, and the PUCCH resource doesnot comprise an orthogonal cover code (OCC). PUCCH format 4 may occupy anumber of OFDM symbols (e.g., between four and fourteen OFDM symbols)and may comprise more than two bits. The wireless device may use PUCCHformat 4, for example, if the transmission is four or more symbols, thequantity/number of UCI bits is two or more, and the PUCCH resourcecomprises an OCC.

The base station may send/transmit configuration parameters to thewireless device for a plurality of PUCCH resource sets, for example,using an RRC message. The plurality of PUCCH resource sets (e.g., up tofour sets in NR, or up to any other quantity of sets in other systems)may be configured on an uplink BWP of a cell. A PUCCH resource set maybe configured with a PUCCH resource set index, a plurality of PUCCHresources with a PUCCH resource being identified by a PUCCH resourceidentifier (e.g., pucch-Resourceid), and/or a number (e.g. a maximumnumber) of UCI information bits the wireless device may send/transmitusing one of the plurality of PUCCH resources in the PUCCH resource set.The wireless device may select one of the plurality of PUCCH resourcesets, for example, based on a total bit length of the UCI informationbits (e.g., HARQ-ACK, SR, and/or CSI) if configured with a plurality ofPUCCH resource sets. The wireless device may select a first PUCCHresource set having a PUCCH resource set index equal to “0,” forexample, if the total bit length of UCI information bits is two orfewer. The wireless device may select a second PUCCH resource set havinga PUCCH resource set index equal to “1,” for example, if the total bitlength of UCI information bits is greater than two and less than orequal to a first configured value. The wireless device may select athird PUCCH resource set having a PUCCH resource set index equal to “2,”for example, if the total bit length of UCI information bits is greaterthan the first configured value and less than or equal to a secondconfigured value. The wireless device may select a fourth PUCCH resourceset having a PUCCH resource set index equal to “3,” for example, if thetotal bit length of UCI information bits is greater than the secondconfigured value and less than or equal to a third value (e.g., 1406,1706, or any other quantity of bits).

The wireless device may determine a PUCCH resource from the PUCCHresource set for UCI (HARQ-ACK, CSI, and/or SR) transmission, forexample, after determining a PUCCH resource set from a plurality ofPUCCH resource sets. The wireless device may determine the PUCCHresource, for example, based on a PUCCH resource indicator in DCI (e.g.,with DCI format 1_0 or DCI for 1_1) received on/via a PDCCH. An n-bit(e.g., a three-bit) PUCCH resource indicator in the DCI may indicate oneof multiple (e.g., eight) PUCCH resources in the PUCCH resource set. Thewireless device may send/transmit the UCI (HARQ-ACK, CSI and/or SR)using a PUCCH resource indicated by the PUCCH resource indicator in theDCI, for example, based on the PUCCH resource indicator.

FIG. 15A shows an example communications between a wireless device and abase station. A wireless device 1502 and a base station 1504 may be partof a communication network, such as the communication network 100 shownin FIG. 1A, the communication network 150 shown in FIG. 1B, or any othercommunication network. A communication network may comprise more thanone wireless device and/or more than one base station, withsubstantially the same or similar configurations as those shown in FIG.15A.

The base station 1504 may connect the wireless device 1502 to a corenetwork (not shown) via radio communications over the air interface (orradio interface) 1506. The communication direction from the base station1504 to the wireless device 1502 over the air interface 1506 may bereferred to as the downlink. The communication direction from thewireless device 1502 to the base station 1504 over the air interface maybe referred to as the uplink. Downlink transmissions may be separatedfrom uplink transmissions, for example, using various duplex schemes(e.g., FDD, TDD, and/or some combination of the duplexing techniques).

For the downlink, data to be sent to the wireless device 1502 from thebase station 1504 may be provided/transferred/sent to the processingsystem 1508 of the base station 1504. The data may beprovided/transferred/sent to the processing system 1508 by, for example,a core network. For the uplink, data to be sent to the base station 1504from the wireless device 1502 may be provided/transferred/sent to theprocessing system 1518 of the wireless device 1502. The processingsystem 1508 and the processing system 1518 may implement layer 3 andlayer 2 OSI functionality to process the data for transmission. Layer 2may comprise an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer,for example, described with respect to FIG. 2A, FIG. 2B, FIG. 3 , andFIG. 4A. Layer 3 may comprise an RRC layer, for example, described withrespect to FIG. 2B.

The data to be sent to the wireless device 1502 may beprovided/transferred/sent to a transmission processing system 1510 ofbase station 1504, for example, after being processed by the processingsystem 1508. The data to be sent to base station 1504 may beprovided/transferred/sent to a transmission processing system 1520 ofthe wireless device 1502, for example, after being processed by theprocessing system 1518. The transmission processing system 1510 and thetransmission processing system 1520 may implement layer 1 OSIfunctionality. Layer 1 may comprise a PHY layer, for example, describedwith respect to FIG. 2A, FIG. 2B, FIG. 3 , and FIG. 4A. Forsending/transmission processing, the PHY layer may perform, for example,forward error correction coding of transport channels, interleaving,rate matching, mapping of transport channels to physical channels,modulation of physical channel, multiple-input multiple-output (MIMO) ormulti-antenna processing, and/or the like.

A reception processing system 1512 of the base station 1504 may receivethe uplink transmission from the wireless device 1502. The receptionprocessing system 1512 of the base station 1504 may comprise one or moreTRPs. A reception processing system 1522 of the wireless device 1502 mayreceive the downlink transmission from the base station 1504. Thereception processing system 1522 of the wireless device 1502 maycomprise one or more antenna panels. The reception processing system1512 and the reception processing system 1522 may implement layer 1 OSIfunctionality. Layer 1 may include a PHY layer, for example, describedwith respect to FIG. 2A, FIG. 2B, FIG. 3 , and FIG. 4A. For receiveprocessing, the PHY layer may perform, for example, error detection,forward error correction decoding, deinterleaving, demapping oftransport channels to physical channels, demodulation of physicalchannels, MIMO or multi-antenna processing, and/or the like.

The base station 1504 may comprise multiple antennas (e.g., multipleantenna panels, multiple TRPs, etc.). The wireless device 1502 maycomprise multiple antennas (e.g., multiple antenna panels, etc.). Themultiple antennas may be used to perform one or more MIMO ormulti-antenna techniques, such as spatial multiplexing (e.g.,single-user MIMO or multi-user MIMO), transmit/receive diversity, and/orbeamforming. The wireless device 1502 and/or the base station 1504 mayhave a single antenna.

The processing system 1508 and the processing system 1518 may beassociated with a memory 1514 and a memory 1524, respectively. Memory1514 and memory 1524 (e.g., one or more non-transitory computer readablemediums) may store computer program instructions or code that may beexecuted by the processing system 1508 and/or the processing system1518, respectively, to carry out one or more of the functionalities(e.g., one or more functionalities described herein and otherfunctionalities of general computers, processors, memories, and/or otherperipherals). The transmission processing system 1510 and/or thereception processing system 1512 may be coupled to the memory 1514and/or another memory (e.g., one or more non-transitory computerreadable mediums) storing computer program instructions or code that maybe executed to carry out one or more of their respectivefunctionalities. The transmission processing system 1520 and/or thereception processing system 1522 may be coupled to the memory 1524and/or another memory (e.g., one or more non-transitory computerreadable mediums) storing computer program instructions or code that maybe executed to carry out one or more of their respectivefunctionalities.

The processing system 1508 and/or the processing system 1518 maycomprise one or more controllers and/or one or more processors. The oneor more controllers and/or one or more processors may comprise, forexample, a general-purpose processor, a digital signal processor (DSP),a microcontroller, an application specific integrated circuit (ASIC), afield programmable gate array (FPGA) and/or other programmable logicdevice, discrete gate and/or transistor logic, discrete hardwarecomponents, an on-board unit, or any combination thereof. The processingsystem 1508 and/or the processing system 1518 may perform at least oneof signal coding/processing, data processing, power control,input/output processing, and/or any other functionality that may enablethe wireless device 1502 and/or the base station 1504 to operate in awireless environment.

The processing system 1508 may be connected to one or more peripherals1516. The processing system 1518 may be connected to one or moreperipherals 1526. The one or more peripherals 1516 and the one or moreperipherals 1526 may comprise software and/or hardware that providefeatures and/or functionalities, for example, a speaker, a microphone, akeypad, a display, a touchpad, a power source, a satellite transceiver,a universal serial bus (USB) port, a hands-free headset, a frequencymodulated (FM) radio unit, a media player, an Internet browser, anelectronic control unit (e.g., for a motor vehicle), and/or one or moresensors (e.g., an accelerometer, a gyroscope, a temperature sensor, aradar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, acamera, and/or the like). The processing system 1508 and/or theprocessing system 1518 may receive input data (e.g., user input data)from, and/or provide output data (e.g., user output data) to, the one ormore peripherals 1516 and/or the one or more peripherals 1526. Theprocessing system 1518 in the wireless device 1502 may receive powerfrom a power source and/or may be configured to distribute the power tothe other components in the wireless device 1502. The power source maycomprise one or more sources of power, for example, a battery, a solarcell, a fuel cell, or any combination thereof. The processing system1508 may be connected to a Global Positioning System (GPS) chipset 1517.The processing system 1518 may be connected to a Global PositioningSystem (GPS) chipset 1527. The GPS chipset 1517 and the GPS chipset 1527may be configured to determine and provide geographic locationinformation of the wireless device 1502 and the base station 1504,respectively.

FIG. 15B shows example elements of a computing device that may be usedto implement any of the various devices described herein, including, forexample, the base station 160A, 160B, 162A, 162B, 220, and/or 1504, thewireless device 106, 156A, 156B, 210, and/or 1502, or any other basestation, wireless device, AMF, UPF, network device, or computing devicedescribed herein. The computing device 1530 may include one or moreprocessors 1531, which may execute instructions stored in therandom-access memory (RAM) 1533, the removable media 1534 (such as aUniversal Serial Bus (USB) drive, compact disk (CD) or digital versatiledisk (DVD), or floppy disk drive), or any other desired storage medium.Instructions may also be stored in an attached (or internal) hard drive1535. The computing device 1530 may also include a security processor(not shown), which may execute instructions of one or more computerprograms to monitor the processes executing on the processor 1531 andany process that requests access to any hardware and/or softwarecomponents of the computing device 1530 (e.g., ROM 1532, RAM 1533, theremovable media 1534, the hard drive 1535, the device controller 1537, anetwork interface 1539, a GPS 1541, a Bluetooth interface 1542, a WiFiinterface 1543, etc.). The computing device 1530 may include one or moreoutput devices, such as the display 1536 (e.g., a screen, a displaydevice, a monitor, a television, etc.), and may include one or moreoutput device controllers 1537, such as a video processor. There mayalso be one or more user input devices 1538, such as a remote control,keyboard, mouse, touch screen, microphone, etc. The computing device1530 may also include one or more network interfaces, such as a networkinterface 1539, which may be a wired interface, a wireless interface, ora combination of the two. The network interface 1539 may provide aninterface for the computing device 1530 to communicate with a network1540 (e.g., a RAN, or any other network). The network interface 1539 mayinclude a modem (e.g., a cable modem), and the external network 1540 mayinclude communication links, an external network, an in-home network, aprovider's wireless, coaxial, fiber, or hybrid fiber/coaxialdistribution system (e.g., a DOCSIS network), or any other desirednetwork. Additionally, the computing device 1530 may include alocation-detecting device, such as a global positioning system (GPS)microprocessor 1541, which may be configured to receive and processglobal positioning signals and determine, with possible assistance froman external server and antenna, a geographic position of the computingdevice 1530.

The example in FIG. 15B may be a hardware configuration, although thecomponents shown may be implemented as software as well. Modificationsmay be made to add, remove, combine, divide, etc. components of thecomputing device 1530 as desired. Additionally, the components may beimplemented using basic computing devices and components, and the samecomponents (e.g., processor 1531, ROM storage 1532, display 1536, etc.)may be used to implement any of the other computing devices andcomponents described herein. For example, the various componentsdescribed herein may be implemented using computing devices havingcomponents such as a processor executing computer-executableinstructions stored on a computer-readable medium, as shown in FIG. 15B.Some or all of the entities described herein may be software based, andmay co-exist in a common physical platform (e.g., a requesting entitymay be a separate software process and program from a dependent entity,both of which may be executed as software on a common computing device).

FIG. 16A shows an example structure for uplink transmission. Processingof a baseband signal representing a physical uplink shared channel maycomprise/perform one or more functions. The one or more functions maycomprise at least one of: scrambling; modulation of scrambled bits togenerate complex-valued symbols; mapping of the complex-valuedmodulation symbols onto one or several transmission layers; transformprecoding to generate complex-valued symbols; precoding of thecomplex-valued symbols; mapping of precoded complex-valued symbols toresource elements; generation of complex-valued time-domain SingleCarrier-Frequency Division Multiple Access (SC-FDMA), CP-OFDM signal foran antenna port, or any other signals; and/or the like. An SC-FDMAsignal for uplink transmission may be generated, for example, iftransform precoding is enabled. A CP-OFDM signal for uplink transmissionmay be generated, for example, if transform precoding is not enabled(e.g., as shown in FIG. 16A). These functions are examples and othermechanisms for uplink transmission may be implemented.

FIG. 16B shows an example structure for modulation and up-conversion ofa baseband signal to a carrier frequency. The baseband signal may be acomplex-valued SC-FDMA, CP-OFDM baseband signal (or any other basebandsignals) for an antenna port and/or a complex-valued Physical RandomAccess Channel (PRACH) baseband signal. Filtering may beperformed/employed, for example, prior to transmission.

FIG. 16C shows an example structure for downlink transmissions.Processing of a baseband signal representing a physical downlink channelmay comprise/perform one or more functions. The one or more functionsmay comprise: scrambling of coded bits in a codeword to besent/transmitted on/via a physical channel; modulation of scrambled bitsto generate complex-valued modulation symbols; mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers; precoding of the complex-valued modulation symbols on a layerfor transmission on the antenna ports; mapping of complex-valuedmodulation symbols for an antenna port to resource elements; generationof complex-valued time-domain OFDM signal for an antenna port; and/orthe like. These functions are examples and other mechanisms for downlinktransmission may be implemented.

FIG. 16D shows an example structure for modulation and up-conversion ofa baseband signal to a carrier frequency. The baseband signal may be acomplex-valued OFDM baseband signal for an antenna port or any othersignal. Filtering may be performed/employed, for example, prior totransmission.

A wireless device may receive, from abase station, one or more messages(e.g. RRC messages) comprising configuration parameters of a pluralityof cells (e.g., a primary cell, one or more secondary cells). Thewireless device may communicate with at least one base station (e.g.,two or more base stations in dual-connectivity) via the plurality ofcells. The one or more messages (e.g. as a part of the configurationparameters) may comprise parameters of PHY, MAC, RLC, PCDP, SDAP, RRClayers for configuring the wireless device. The configuration parametersmay comprise parameters for configuring PHY and MAC layer channels,bearers, etc. The configuration parameters may comprise parametersindicating values of timers for PHY, MAC, RLC, PCDP, SDAP, RRC layers,and/or communication channels.

A timer may begin running, for example, if it is started, and continuerunning until it is stopped or until it expires. A timer may be started,for example, if it is not running or restarted if it is running. A timermay be associated with a value (e.g., the timer may be started orrestarted from a value or may be started from zero and expire if itreaches the value). The duration of a timer may not be updated, forexample, until the timer is stopped or expires (e.g., due to BWPswitching). A timer may be used to measure a time period/window for aprocess. With respect to an implementation and/or procedure related toone or more timers or other parameters, it will be understood that theremay be multiple ways to implement the one or more timers or otherparameters. One or more of the multiple ways to implement a timer may beused to measure a time period/window for the procedure. A random accessresponse window timer may be used for measuring a window of time forreceiving a random access response. The time difference between two timestamps may be used, for example, instead of starting a random accessresponse window timer and determine the expiration of the timer. Aprocess for measuring a time window may be restarted, for example, if atimer is restarted. Other example implementations may beconfigured/provided to restart a measurement of a time window.

Two or more component carriers (CCs) may be aggregated, for example, ina carrier aggregation (CA). A wireless device may simultaneously receiveand/or transmit on one or more CCs, for example, depending oncapabilities of the wireless device. The CA may be supported forcontiguous CCs. The CA may be supported for non-contiguous CCs.

A wireless device may have one RRC connection with a network, forexample, if configured with CA. At (e.g., during) an RRC connectionestablishment, re-establishment and/or handover, a cell providing a NASmobility information may be a serving cell. At (e.g., during) an RRCconnection re-establishment and/or handover procedure, a cell providinga security input may be a serving cell. The serving cell may be referredto as a primary cell (PCell). A base station may send (e.g., transmit),to a wireless device, one or more messages comprising configurationparameters of a plurality of one or more secondary cells (SCells), forexample, depending on capabilities of the wireless device.

A base station and/or a wireless device may use an activation and/ordeactivation mechanism of an SCell for an efficient battery consumption,for example, if the base station and/or the wireless device isconfigured with CA. A base station may activate or deactivate at leastone of the one or more SCells, for example, if the wireless device isconfigured with one or more SCells. The SCell may be deactivated, forexample, after or upon configuration of an SCell.

A wireless device may activate and/or deactivate an SCell, for example,after or in response to receiving an SCell activation and/ordeactivation MAC CE. A base station may send (e.g., transmit), to awireless device, one or more messages comprising anSCellDeactivationTimer timer. The wireless device may deactivate anSCell, for example, after or in response to an expiry of thesCellDeactivationTimer timer.

A wireless device may activate an SCell, for example, if the wirelessdevice receives an SCell activation/deactivation MAC CE activating anSCell. The wireless device may perform operations (e.g., after or inresponse to the activating the SCell) that may comprise: SRStransmissions on the SCell; CQI, PMI, RI, and/or CRI reporting for theSCell on a PCell; PDCCH monitoring on the SCell; PDCCH monitoring forthe SCell on the PCell; and/or PUCCH transmissions on the SCell.

The wireless device may start and/or restart a timer (e.g., anSCellDeactivationTimer timer) associated with the SCell, for example,after or in response to activating the SCell. The wireless device maystart the timer (e.g., sCellDeactivationTimer timer) in the slot, forexample, if the SCell activation/deactivation MAC CE has been received.The wireless device may initialize and/or re-initialize one or moresuspended configured uplink grants of a configured grant Type 1associated with the SCell according to a stored configuration, forexample, after or in response to activating the SCell. The wirelessdevice may trigger a PHR, for example, after or in response toactivating the SCell.

The wireless device may deactivate the activated SCell, for example, ifthe wireless device receives an SCell activation/deactivation MAC CEdeactivating an activated SCell. The wireless device may deactivate theactivated SCell, for example, if a timer (e.g., anSCellDeactivationTimer timer) associated with an activated SCellexpires. The wireless device may stop the timer (e.g.,SCellDeactivationTimer timer) associated with the activated SCell, forexample, after or in response to deactivating the activated SCell. Thewireless device may clear one or more configured downlink assignmentsand/or one or more configured uplink grant Type 2 associated with theactivated SCell, for example, after or in response to the deactivatingthe activated SCell. The wireless device may suspend one or moreconfigured uplink grant Type 1 associated with the activated SCell,and/or flush HARQ buffers associated with the activated SCell, forexample, after or in response to deactivating the activated SCell.

A wireless device may refrain from performing certain operations, forexample, if an SCell is deactivated. The wireless device may refrainfrom performing one or more of the following operations if an SCell isdeactivated: transmitting SRS on the SCell; reporting CQI, PMI, RI,and/or CRI for the SCell on a PCell; transmitting on UL-SCH on theSCell; transmitting on a RACH on the SCell; monitoring at least onefirst PDCCH on the SCell; monitoring at least one second PDCCH for theSCell on the PCell; and/or transmitting a PUCCH on the SCell.

A wireless device may restart a timer (e.g., an SCellDeactivationTimertimer) associated with the activated SCell, for example, if at least onefirst PDCCH on an activated SCell indicates an uplink grant or adownlink assignment. A wireless device may restart a timer (e.g., anSCellDeactivationTimer timer) associated with the activated SCell, forexample, if at least one second PDCCH on a serving cell (e.g. a PCell oran SCell configured with PUCCH, such as a PUCCH SCell) scheduling theactivated SCell indicates an uplink grant and/or a downlink assignmentfor the activated SCell. A wireless device may abort the ongoing randomaccess procedure on the SCell, for example, if an SCell is deactivatedand/or if there is an ongoing random access procedure on the SCell.

FIG. 17A shows an example of an SCell activation/deactivation MAC CEthat may comprise one octet. A first MAC PDU subheader comprising afirst LCID (e.g., LCID 111010) may indicate/identify the SCellactivation/deactivation MAC CE of one octet. An SCellactivation/deactivation MAC CE of one octet may have a fixed size. TheSCell activation/deactivation MAC CE of one octet may comprise a singleoctet. The single octet may comprise a first number of C-fields (e.g.,seven) and a second number of R-fields (e.g., one).

FIG. 17B shows an example of an SCell Activation/Deactivation MAC CE offour octets. A second MAC PDU subheader with a second LCID (e.g., LCID111001) may indicate/identify the SCell Activation/Deactivation MAC CEof four octets. An SCell activation/deactivation MAC CE of four octetsmay have a fixed size. The SCell activation/deactivation MAC CE of fouroctets may comprise four octets. The four octets may comprise a thirdnumber of C-fields (e.g., 31) and a fourth number of R-fields (e.g., 1).A C_(i) field may indicate an activation/deactivation status of an SCellwith an SCell index i, for example, if an SCell with SCell index i isconfigured. An SCell with an SCell index i may be activated, forexample, if the C_(i) field is set to one. An SCell with an SCell indexi may be deactivated, for example, if the C_(i) field is set to zero.The wireless device may ignore the C_(i) field, for example, if there isno SCell configured with SCell index i. An R field may indicate areserved bit. The R field may be set to zero.

A base station and/or a wireless device may use a power saving mechanism(e.g., hibernation mechanism) for an SCell, for example, if CA isconfigured. A power saving mechanism may improve battery performance(e.g., run-times), reduce power consumption of the wireless device,and/or to improve latency of SCell activation and/or SCell addition. TheSCell may be transitioned (e.g., switched and/or adjusted) to a dormantstate if the wireless device initiates a power saving state for (e.g.,hibernates) the SCell. The wireless device may, for example, if theSCell is transitioned to a dormant state: stop transmitting SRS on theSCell, report CQI/PMI/RI/PTI/CRI for the SCell according to or based ona periodicity configured for the SCell in a dormant state, not transmiton an UL-SCH on the SCell, not transmit on a RACH on the SCell, notmonitor the PDCCH on the SCell, not monitor the PDCCH for the SCell,and/or not transmit PUCCH on the SCell. Not transmitting, notmonitoring, not receiving, and/or not performing an action may comprise,for example, refraining from transmitting, refraining from monitoring,refraining from receiving, and/or refraining from performing an action,respectively. Reporting CSI for an SCell, that has been transitioned toa dormant state, and not monitoring the PDCCH on/for the SCell, mayprovide the base station an “always-updated” CSI for the SCell. The basestation may use a quick and/or accurate channel adaptive scheduling onthe SCell, based on the always-updated CSI, if the SCell is transitionedback to active state. Using the always-updated CSI may speed up anactivation procedure of the SCell. Reporting CSI for the SCell and notmonitoring the PDCCH on and/or for the SCell (e.g., that may have beentransitioned to a dormant state), may provide advantages such asincreased battery efficiency, reduced power consumption of the wirelessdevice, and/or increased timeliness and/or accuracy of channel feedbackinformation feedback. A PCell/PSCell and/or a PUCCH SCell, for example,may not be configured or transitioned to a dormant state.

A base station may activate, hibernate, or deactivate at least one ofone or more configured SCells. A base station may send (e.g., transmit)to a wireless device, for example, one or more messages comprisingparameters indicating at least one SCell being set to an active state, adormant state, or an inactive state.

A base station may transmit, for example, one or more RRC messagescomprising parameters indicating at least one SCell being set to anactive state, a dormant state, or an inactive state. A base station maytransmit, for example, one or more MAC control elements (CEs) comprisingparameters indicating at least one SCell being set to an active state, adormant state, or an inactive state.

The wireless device may perform (e.g., if the SCell is in an activestate): SRS transmissions on the SCell, CQI/PMI/RI/CRI reporting for theSCell, PDCCH monitoring on the SCell, PDCCH monitoring for the SCell,and/or PUCCH/SPUCCH transmissions on the SCell. The wireless device may(e.g., if the SCell is in an inactive state): not transmit SRS on theSCell, not report CQI/PMI/RI/CRI for the SCell, not transmit on anUL-SCH on the SCell, not transmit on a RACH on the SCell, not monitorPDCCH on the SCell, not monitor a PDCCH for the SCell; and/or nottransmit a PUCCH/SPUCCH on the SCell. The wireless device may (e.g., ifthe SCell is in a dormant state): not transmit SRS on the SCell, reportCQI/PMI/RI/CRI for the SCell, not transmit on a UL-SCH on the SCell, nottransmit on a RACH on the SCell, not monitor a PDCCH on the SCell, notmonitor a PDCCH for the SCell, and/or not transmit a PUCCH/SPUCCH on theSCell.

A base station may send (e.g., transmit), for example, a first MAC CE(e.g., an activation/deactivation MAC CE as shown in FIGS. 17A and 17B).The first MAC CE may indicate, to a wireless device, activation ordeactivation of at least one SCell. A C_(i) field may indicate anactivation/deactivation status of an SCell with an SCell index i, forexample, if an SCell with SCell index i is configured. An SCell with anSCell index i may be activated, for example, if the C_(i) field is setto one. An SCell with an SCell index i may be deactivated, for example,if the C_(i) field is set to zero. A wireless device receiving a MAC CEmay ignore the C_(i) field, for example, if there is no SCell configuredwith SCell index i. An R field may indicate a reserved bit. The R fieldmay be set to zero.

A base station may send (e.g., transmit) a MAC CE (e.g., a hibernationMAC CE) that may generally be referred to herein as a second MAC CE. Thesecond MAC CE may be the same as or different from other MAC CEsdescribed herein, but is generally referred to herein as the second MACCE. The second MAC CE may indicate activation and/or hibernation of atleast one SCell to a wireless device. The second MAC CE may beassociated with, for example, a second LCID different from a first LCIDof the first MAC CE (e.g., the activation/deactivation MAC CE). Thesecond MAC CE may have a fixed size. The second MAC CE may comprise asingle octet comprising seven C-fields and one R-field.

FIG. 18A shows an example of a MAC CE (e.g., the second MAC CEreferenced above) comprising a single octet. The second MAC CE maycomprise four octets comprising 31 C-fields and one R-field. FIG. 18Bshows an example of the second MAC CE comprising four octets. A secondMAC CE (e.g., comprising four octets) may be associated with a thirdLCID. The third LCID may be different from the second LCID for thesecond MAC CE and/or the first LCID for activation/deactivation MAC CE.The second MAC CE (e.g., comprising one octet) may be used, for example,if there is no SCell with a serving cell index greater than a value(e.g., 7 or any other value). The second MAC CE (e.g., comprising fouroctets) may be used, for example, if there is an SCell with a servingcell index greater than a value (e.g., 7 or any other value). A secondMAC CE may indicate a dormant/activated status of an SCell, for example,if a second MAC CE is received and a first MAC CE is not received. TheC_(i) field of the second MAC CE may indicate a dormant/activated statusof an SCell with SCell index i if there is an SCell configured withSCell index i, otherwise the MAC entity may ignore the C_(i) field. Awireless device may transition an SCell associated with SCell index iinto a dormant state, for example, if C_(i) of the second MAC CE is setto “1”. The wireless device may activate an SCell associated with SCellindex i, for example, if C_(i) of the second MAC CE is set to “0”. Thewireless device may activate the SCell with SCell index i, for example,if C_(i) of the second MAC CE is set to “0” and the SCell with SCellindex i is in a dormant state. The wireless device may ignore the C_(i)field of the second MAC CE, for example, if the C_(i) field is set to“0” and the SCell with SCell index i is not in a dormant state.

FIG. 18C shows example configurations of a field of the first MAC CE.The field may comprise, for example, a C_(i) field of the first MAC CE(e.g., an activation/deactivation MAC CE), a C_(i) field of the secondMAC CE (e.g., a hibernation MAC CE), and corresponding resulting SCellstatus (e.g., activated/deactivated/dormant). The wireless device maydeactivate an SCell associated with SCell index i, for example, if C_(i)of hibernation MAC CE is set to 0, and C_(i) of theactivation/deactivation MAC CE is set to 0. The wireless device mayactivate an SCell associated with SCell index i, for example, if C_(i)of hibernation MAC CE is set to 0, and C_(i) of theactivation/deactivation MAC CE is set to 1. The wireless device mayignore the hibernation MAC CE and the activation/deactivation MAC CE,for example, if C_(i) of hibernation MAC CE is set to 1, and C_(i) ofthe activation/deactivation MAC CE is set to 0. The wireless device maytransition an SCell associated with SCell index I to a dormant state,for example, if C_(i) of hibernation MAC CE is set to 1, and C_(i) ofthe activation/deactivation MAC CE is set to 1.

A base station may activate, hibernate, and/or deactivate at least oneof one or more SCells, for example, if the base station is configuredwith the one or more SCells. A base station and/or a wireless device maymaintain an SCell deactivation timer (e.g., SCellDeactivationTimer), forexample, per a configured SCell and/or except for an SCell configuredwith PUCCH/SPUCCH, if any. The base station and/or the wireless devicemay deactivate an associated SCell, for example, if an SCelldeactivation timer expires. A base station and/or a wireless device maymaintain dormant SCell deactivation timer (e.g.,dormantSCellDeactivationTimer), for example, per a configured SCelland/or except for an SCell configured with PUCCH/SPUCCH, if any. Thebase station and/or the wireless device may deactivate an associatedSCell, for example, if the dormant SCell deactivation timer expires(e.g., if the SCell is in dormant state).

A base station and/or a wireless device may, for example, maintain anSCell hibernation timer (e.g., SCellHibernationTimer), for example, pera configured SCell and/or except for an SCell configured withPUCCH/SPUCCH, if any. The base station (and/or the wireless device mayhibernate an associated SCell, for example, if the SCell hibernationtimer expires (e.g., if the SCell is in active state). The SCellhibernation timer may take priority over the SCell deactivation timer,for example, if both the SCell deactivation timer and the SCellhibernation timer are configured. A base station and/or a wirelessdevice may ignore the SCell deactivation timer regardless of the SCelldeactivation timer expiry, for example, if both the SCell deactivationtimer and the SCell hibernation timer are configured.

A wireless device (e.g., MAC entity of a wireless device) may activatean SCell, for example, if the MAC entity is configured with an activatedSCell at SCell configuration. A wireless device may activate an SCell,for example, if the wireless device receives a MAC CE(s) activating theSCell. The wireless device may start or restart an SCell deactivationtimer associated with an SCell, for example, based on or in response toactivating the SCell. The wireless device may start or restart an SCellhibernation timer (e.g., if configured) associated with an SCell, forexample, based on or in response to activating the SCell. A wirelessdevice may trigger a PHR procedure, for example, based on or in responseto activating an SCell.

A wireless device may deactivate the SCell, for example, if the wirelessdevice receives a MAC CE(s) indicating deactivation of an SCell. Thewireless device may: deactivate the SCell; stop an SCell deactivationtimer associated with the SCell; and/or flush all HARQ buffersassociated with the SCell, for example, if the wireless device receivesa MAC CE(s) indicating deactivation of an SCell. The wireless devicemay: deactivate the SCell; stop the SCell deactivation timer associatedwith the SCell; and/or flush all HARQ buffers associated with the SCell,for example, if an SCell deactivation timer associated with an activatedSCell expires and an SCell hibernation timer is not configured.

A wireless device and/or a base station may (e.g., if a first PDCCH onan SCell indicates an uplink grant or downlink assignment, or a secondPDCCH on a serving cell scheduling the SCell indicates an uplink grantor a downlink assignment for the SCell, or a MAC PDU is transmitted in aconfigured uplink grant or received in a configured downlink assignment)restart an SCell deactivation timer associated with an activated SCelland/or restart an SCell hibernation timer (e.g., if configured)associated with the SCell. An ongoing random access (RA) procedure on anSCell may be aborted, for example, if, the SCell is deactivated.

A wireless device and/or a base station may (e.g., if configured with anSCell associated with an SCell state set to dormant state upon the SCellconfiguration, or if receiving MAC CE(s) and/or DCI(s) indicatingtransitioning the SCell to a dormant state): set (e.g., transition) theSCell to a dormant state, transmit one or more CSI reports for theSCell, stop an SCell deactivation timer associated with the SCell, stopan SCell hibernation timer (if configured) associated with the SCell,start or restart a dormant SCell deactivation timer associated with theSCell, and/or flush all HARQ buffers associated with the SCell. Thewireless device and/or a base station may (e.g., if the SCellhibernation timer associated with the activated SCell expires):hibernate the SCell, stop the SCell deactivation timer associated withthe SCell, stop the SCell hibernation timer associated with the SCell,and/or flush all HARQ buffers associated with the SCell. The wirelessdevice and/or a base station may (e.g., if a dormant SCell deactivationtimer associated with a dormant SCell expires): deactivate the SCelland/or stop the dormant SCell deactivation timer associated with theSCell. Ongoing RA procedure on an SCell may be aborted, for example, ifthe SCell is in dormant state. The wireless device may not monitor anydownlink control channel for/of the SCell, for example, if the SCell isin the dormant state.

FIG. 19 shows example DCI formats. The example DCI formats maycorrespond to an operation such as an FDD operation (e.g., 20 MHzbandwidth, or any other bandwidth). The example DCI formats maycorrespond to transmissions involving two transmission antennas (or anyother number of antennas) at the base station. The example DCI formatsmay correspond to transmissions utilizing CA or not utilizing no carrieraggregation. The DCI formats may comprise at least one of: DCI format0_0/0_1 indicating scheduling of PUSCH in a cell; DCI format 1_0/1_1indicating scheduling of PDSCH in a cell; DCI format 2_0 indicating aslot format (e.g., to a group of wireless devices); DCI format 2_1indicating PRB(s) and/or OFDM symbol(s) to a group of wireless devices(e.g., in a scenario where a wireless device may assume no transmissionis intended for the wireless device); DCI format 2_2 indicatingtransmission of TPC commands for PUCCH and PUSCH; and/or DCI format 2_3indicating transmission of a group of TPC commands for SRS transmissionby one or more wireless devices. A base station may transmit DCI, via aPDCCH, for scheduling decisions and/or power-control commands. The DCImay comprise at least one of: downlink scheduling assignments, uplinkscheduling grants, power-control commands. The downlink schedulingassignments may comprise at least one of: PDSCH resource indication,transport format, HARQ information, control information related tomultiple antenna schemes, and/or a command for power control of thePUCCH used for transmission of ACK/NACK (e.g., based on downlinkscheduling assignments). The uplink scheduling grants may comprise atleast one of: PUSCH resource indication, transport format, and HARQrelated information, and/or a power control command of the PUSCH.

The different types of control information correspond to different DCImessage sizes. Supporting spatial multiplexing with non-contiguousallocation of RBs (e.g., in the frequency domain) may require a largerscheduling message, for example, in comparison with an uplink grant thatallows only contiguous allocation of RBs. The DCI may be categorizedinto different DCI formats. A DCI format may correspond to a certainmessage size and may be associated with a particular application/usage.

A wireless device may monitor one or more PDCCH candidates to detect oneor more DCI with one or more DCI format. One or more PDCCH transmissionsmay be transmitted in a common search space or a wirelessdevice-specific search space. A wireless device may monitor PDCCH withonly a limited set of DCI formats, for example, to reduce powerconsumption. A wireless device may not be required to detect DCI, forexample, with DCI format 6 (e.g., as used for an eMTC wireless device),and/or any other DCI format. A wireless device with a capability fordetection of a higher number of DCI formats may have a higher powerconsumption.

The one or more PDCCH candidates that a wireless device monitors may bedefined in terms of PDCCH wireless device-specific search spaces. APDCCH wireless device-specific search space at CCE aggregation level L(e.g., L∈{1,2,4,8}) may be defined by a set of PDCCH candidates for theCCE aggregation level L. A wireless device may be configured (e.g., byone or more higher layer parameters), for a DCI format per serving cell,a quantity of PDCCH candidates per CCE aggregation level L.

A wireless device may monitor one or more PDCCH candidate in controlresource set q based on a periodicity of symbols (e.g., W_(PDCCH,q)symbols) for control resource set q. The periodicity of the symbols forthe control resource set q may be configured, for example, by one ormore higher layer parameters)

Information in the DCI formats used for downlink scheduling may beorganized into different groups. Fields present in DCIs corresponding todifferent DCI formats may be different. The fields may comprise, forexample, at least one of: resource information (e.g., comprising carrierindicator (e.g., 0 or 3 bits, or any other quantity of bits) and/or RBallocation); HARQ process number; MCS, new data indicator (NDI), andredundancy version (RV) (e.g., for a first TB); MCS, NDI and RV (e.g.,for a second TB); MIMO related information; PDSCH resource-elementmapping and QCI; downlink assignment index (DAI); TPC for PUCCH; SRSrequest (e.g., 1 bit, or any other quantity of bits), an indicator fortriggering one-shot SRS transmission; ACK/NACK offset; DCI format 0/1Aindication (e.g., used to differentiate between DCI format 1A and DCIformat 0); and padding (e.g., if necessary). The MIMO relatedinformation may comprise, for example, at least one of: PMI, precodinginformation, transport block swap flag, power offset between PDSCH andreference signal, reference-signal scrambling sequence, number/quantityof layers, and/or antenna ports for transmission.

Information in the DCI formats used for uplink scheduling may beorganized into different groups. Fields present in DCIs corresponding todifferent DCI formats may be different. The fields may comprise, forexample, at least one of: resource information (e.g., comprising carrierindicator, resource allocation type, and/or RB allocation); MCS, NDI(for a first TB); MCS, NDI (for a second TB); phase rotation of anuplink DMRS; precoding information; CSI request, an indicator requestingan aperiodic CSI report; SRS request (e.g., 2 bits, or any otherquantity of bits) to trigger aperiodic SRS transmission (e.g., using oneof up to three preconfigured settings); uplink index/DAI; TPC for PUSCH;DCI format 0/1A indication; and padding (e.g., if necessary).

A base station may perform cyclic redundancy check (CRC) scrambling forDCI, for example, before transmitting the DCI via a PDCCH. The basestation may perform CRC scrambling, for example, by bit-wise addition(or Modulo-2 addition, exclusive OR (XOR) operation, or any othermethod) of multiple bits of at least one wireless device identifier(e.g., C-RNTI, CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, SPCSI C-RNTI, SRS-TPC-RNTI, INT-RNTI, SFI-RNTI, P-RNTI, SI-RNTI, RA-RNTI,MCS-C-RNTI, and/or any other identifier) with the CRC bits of the DCI.The wireless device may check the CRC bits of the DCI, for example, ifdetecting the DCI. The wireless device may receive the DCI, for example,if the CRC is scrambled by a sequence of bits that is the same as the atleast one wireless device identifier.

A base station may transmit one or more PDCCH in different controlresource sets, for example, to support wide bandwidth operation. A basestation may transmit one or more RRC message comprising configurationparameters of one or more control resource sets. At least one of the oneor more control resource sets may comprise, for example, at least oneof: a first OFDM symbol; a number/quantity of consecutive OFDM symbols;a set of resource blocks; a CCE-to-REG mapping; and/or a REG bundle size(e.g., for interleaved CCE-to-REG mapping).

A base station may configure a wireless device with BWPs (e.g., UL BWPsand/or DL BWPs) to enable BA on a PCell. The base station may configurethe wireless device with at least DL BWP(s) (e.g., there may be no ULBWPs in the UL) to enable BA on an SCell (e.g., if CA is configured). Aninitial active BWP may be a first BWP used for initial access, forexample, for the PCell. A first active BWP may be a second BWPconfigured for the wireless device to operate on the SCell (e.g., uponthe SCell being activated). A base station and/or a wireless device mayindependently switch a DL BWP and an UL BWP, for example, if operatingin a paired spectrum (e.g., FDD). A base station and/or a wirelessdevice may simultaneously switch a DL BWP and an UL BWP, for example, ifoperating in an unpaired spectrum (e.g., TDD).

A base station and/or a wireless device may switch a BWP betweenconfigured BWPs, for example, based on DCI, a BWP inactivity timer,and/or any trigger. A base station and/or a wireless device may switchan active BWP to a default BWP, for example, based on or in response toan expiry of a BWP inactivity timer, if configured, associated with aserving cell. The default BWP may be configured by the network.

One UL BWP for each uplink carrier and/or one DL BWP may be active at atime in an active serving cell, for example, for FDD systems that may beconfigured with BA. One DL/UL BWP pair may be active at a time in anactive serving cell, for example, for TDD systems. Operating on the oneUL BWP and/or the one DL BWP (or the one DL/UL BWP pair) may improvewireless device battery consumption. BWPs other than the one active ULBWP and/or the one active DL BWP that the wireless device may work onmay be deactivated. On or for deactivated BWPs, the wireless device maynot monitor PDCCH and/or may not transmit on a PUCCH, PRACH, and/orUL-SCH.

A serving cell may be configured with any quantity of BWPs (e.g., up tofour, or up to any other quantity of BWPs). There may be, for example,one or any other quantity of active BWPs at any point in time for anactivated serving cell.

BWP switching for a serving cell may be used, for example, to activatean inactive BWP and/or deactivate an active BWP (e.g., at a time t). TheBWP switching may be controlled, for example, by a PDCCH indicating adownlink assignment and/or an uplink grant. The BWP switching may becontrolled, for example, by a BWP inactivity timer (e.g.,bwp-InactivityTimer). The BWP switching may be controlled, for example,by a base station (e.g., a MAC entity of a base station), a wirelessdevice (e.g., a MAC entity of a wireless device), and/or a MAC entity,based on or in response to initiating an RA procedure. One or more BWPsmay be initially active, without receiving a PDCCH indicating a downlinkassignment or an uplink grant, for example, if an SPCell is added and/orif an SCell is activated. The active BWP for a serving cell may beindicated by RRC message and/or PDCCH. A DL BWP may be paired with an ULBWP. BWP switching may be common for both UL and DL, for example, forunpaired spectrum.

FIG. 20 shows an example of BWP switching for an SCell. A base station2005 may send (e.g., transmit) one or more messages, to a wirelessdevice 2010. The one or more messages may be for configuring BWPscorresponding to the SCell 2015. The one or more messages may comprise,for example, one or more RRC messages (e.g., RRC connectionreconfiguration message, and/or RRC connection reestablishment message,and/or RRC connection setup message). The configured BWPs may compriseBWP 0, BWP 1, . . . BWP n. The BWP 0 may be configured as a default BWP.The BWP 1 may be configured as a first active BWP. At time n, the basestation 2005 may send (e.g., transmit) an RRC message and/or a MAC CEfor activating the SCell. At or after time n+k, and based on thereception of the RRC message and/or the MAC CE, the wireless device 2010may activate the SCell and start monitoring a PDCCH on the BWP 1 (e.g.,the first active BWP). At or after time m, the base station 2005 maysend (e.g., transmit) DCI for DL assignment or UL grant on the BWP 1. Ator after time m+1, the wireless device 2010 may receive a packet on theBWP 1 and may start a BWP inactivity timer (e.g., bwp-InactivityTimer).At time s, the BWP inactivity timer may expire. At or after time s+t, aBWP may switch to BWP 0 based on expiration of the BWP inactivity timer.BWP switching may comprise, for example, activating the BWP 0 anddeactivating the BWP 1. At time o, the base station 2005 may send (e.g,transmit) an RRC message and/or a MAC CE for deactivating an SCell. Ator after time o+p, the wireless device 2010 may stop the BWP inactivitytimer and deactivate the SCell 2015.

A wireless device may receive RRC message comprising parameters of aSCell and one or more BWP configuration associated with the SCell. TheRRC message may comprise: RRC connection reconfiguration message (e.g.,RRCReconfiguration); RRC connection reestablishment message (e.g.,RRCRestablishment); and/or RRC connection setup message (e.g.,RRCSetup). Among the one or more BWPs, at least one BWP may beconfigured as the first active BWP (e.g., BWP 1 in FIG. 20 ), one BWP asthe default BWP (e.g., BWP 0 in FIG. 20 ). The wireless device mayreceive a MAC CE to activate the SCell at n^(th) slot. The wirelessdevice may start a SCell deactivation timer (e.g.,SCellDeactivationTimer), and start CSI related actions for the SCell,and/or start CSI related actions for the first active BWP of the SCell.The wireless device may start monitoring a PDCCH on BWP 1 in response toactivating the SCell.

The wireless device may start restart a BWP inactivity timer (e.g.,bwp-InactivityTimer) at m^(th) slot in response to receiving DCIindicating DL assignment on BWP 1. The wireless device may switch backto the default BWP (e.g., BWP 0) as an active BWP when the BWPinactivity timer expires, at s^(th) slot. The wireless device maydeactivate the SCell and/or stop the BWP inactivity timer when the SCelldeactivation timer expires.

Using the BWP inactivity timer may reduce a wireless device's powerconsumption, for example, if the wireless device is configured withmultiple cells with each cell having wide bandwidth (e.g., 1 GHzbandwidth, etc.). The wireless device may only transmit on or receivefrom a narrow-bandwidth BWP (e.g., 5 MHz) on the PCell or SCell if thereis no activity on an active BWP.

A MAC entity may perform operations, on an active BWP for an activatedserving cell (e.g., configured with a BWP), comprising: transmitting onan UL-SCH; transmitting on a RACH, monitoring a PDCCH, transmitting on aPUCCH, receiving DL-SCH, and/or (re-) initializing any suspendedconfigured uplink grants of configured grant Type 1 according to astored configuration, if any. On an inactive BWP for each activatedserving cell configured with a BWP, a MAC entity may, for example: nottransmit on an UL-SCH, not transmit on a RACH, not monitor a PDCCH, nottransmit on a PUCCH, not transmit an SRS, not receive a DL-SCHtransmission, clear configured downlink assignment(s) and/or configureduplink grant(s) of configured grant Type 2, and/or suspend configureduplink grant(s) of configured Type 1. A wireless device may perform theBWP switching to a BWP indicated by the PDCCH, for example, if thewireless device (e.g., a MAC entity of the wireless device) receives aPDCCH for a BWP switching of a serving cell and a RA procedureassociated with this serving cell is not ongoing.

A bandwidth part indicator field value may indicate an active DL BWP,from a configured DL BWP set, for DL receptions for example, if thebandwidth part indicator field is configured in DCI format 1_1. Abandwidth part indicator field value, may indicate an active UL BWP,from a configured UL BWP set, for UL transmissions, for example, if thebandwidth part indicator field is configured in DCI format 0_1.

A wireless device may be provided by a higher layer parameter a timervalue corresponding to a BWP inactivity timer for the PCell (e.g.,bwp-InactivityTimer). The wireless device may increment the timer, ifrunning, for example, every interval of 1 millisecond (or any otherfirst duration) for frequency range 1 (or any other first frequencyrange) or every 0.5 milliseconds (or any other second duration) forfrequency range 2 (or any other second frequency range), for example,if: the wireless device does not detect DCI format 1_1 for pairedspectrum operation, or the wireless device does not detect DCI format1_1 or DCI format 0_1 for unpaired spectrum operation, in the interval.

Wireless device procedures on an SCell may be similar to or the same asprocedures on a PCell, for example, if the wireless device is configuredfor the SCell with a higher layer parameter indicating a default DL BWPamong configured DL BWPs (e.g., Default-DL-BWP), and/or if the wirelessdevice is configured with a higher layer parameter indicating a timervalue (e.g., bwp-InactivityTimer). The wireless device procedures on theSCell may use the timer value for the SCell and the default DL BWP forthe SCell. The wireless device may use, as first active DL BWP and firstactive UL BWP on the SCell or secondary cell, an indicated DL BWP and anindicated UL BWP on the SCell, respectively, if a wireless device isconfigured, for example, by a higher layer parameter for the DL BWP(e.g., active-BWP-DL-SCell), and/or by a higher layer parameter for theUL BWP on the SCell or secondary cell (e.g., active-BWP-UL-SCell).

A wireless device may transmit uplink control information (UCI) via oneor more PUCCH resources to a base station. The wireless device maytransmit the one or more UCI, for example, as part of a DRX operation.The one or more UCI may comprise at least one of: HARQ-ACK information;scheduling request (SR); and/or CSI report. A PUCCH resource may beidentified by at least: frequency location (e.g., starting PRB); and/ora PUCCH format associated with initial cyclic shift of a base sequenceand time domain location (e.g., starting symbol index). A PUCCH formatmay be PUCCH format 0, PUCCH format 1, PUCCH format 2, PUCCH format 3,or PUCCH format 4. A PUCCH format 0 may have a length of 1 or 2 OFDMsymbols and be less than or equal to 2 bits. A PUCCH format 1 may occupya number between 4 and 14 of OFDM symbols and be less than or equal to 2bits. A PUCCH format 2 may occupy 1 or 2 OFDM symbols and be greaterthan 2 bits. A PUCCH format 3 may occupy a number between 4 and 14 ofOFDM symbols and be greater than 2 bits. A PUCCH format 4 may occupy anumber between 4 and 14 of OFDM symbols and be greater than 2 bits. ThePUCCH formats 1, 2, 3, and/or 4 may comprise any other quantity of OFDMsymbols and/or any other quantity of bits. The PUCCH resource may beconfigured on a PCell, or a PUCCH secondary cell.

A base station may transmit to a wireless device (e.g., if the wirelessdevice is configured with multiple uplink BWPs), one or more RRCmessages comprising configuration parameters of one or more PUCCHresource sets (e.g., at most 4 sets) on an uplink BWP of the multipleuplink BWPs. Each PUCCH resource set may be configured with a PUCCHresource set index, a list of PUCCH resources with each PUCCH resourcebeing identified by a PUCCH resource identifier (e.g.,pucch-Resourceid), and/or a maximum number of UCI information bits awireless device may transmit using one of the plurality of PUCCHresources in the PUCCH resource set.

A wireless device may select (e.g., if the wireless device is configuredwith multiple uplink BWPs) one of the one or more PUCCH resource setsbased on a total bit length of UCI information bits (e.g., HARQ-ARQbits, SR, and/or CSI) the wireless device will transmit. The wirelessdevice may select a first PUCCH resource set (e.g., with the PUCCHresource set index equal to 0, or any other PUCCH resource set index),for example, if the total bit length of UCI information bits is lessthan or equal to 2 bits (or any other quantity of bits). The wirelessdevice may select a second PUCCH resource set (e.g., with a PUCCHresource set index equal to 1), for example, if the total bit length ofUCI information bits is greater than 2 (or any other quantity of bits)and less than or equal to a first configured value. The wireless devicemay select a third PUCCH resource set (e.g., with a PUCCH resource setindex equal to 2), for example, if the total bit length of UCIinformation bits is greater than the first configured value and lessthan or equal to a second configured value. The wireless device mayselect a fourth PUCCH resource set (e.g., with a PUCCH resource setindex equal to 3), for example, if the total bit length of UCIinformation bits is greater than the second configured value and lessthan or equal to a third value.

A wireless device may determine, for example, based on a quantity ofuplink symbols of UCI transmission and a quantity of UCI bits, a PUCCHformat from a plurality of PUCCH formats comprising PUCCH format 0,PUCCH format 1, PUCCH format 2, PUCCH format 3 and/or PUCCH format 4.The wireless device may transmit UCI in a PUCCH using PUCCH format 0,for example, if the transmission is during, greater than, or over 1symbol or 2 symbols and/or the quantity of HARQ-ACK information bitswith positive or negative SR (HARQ-ACK/SR bits) is 1 or 2. The wirelessdevice may transmit UCI in a PUCCH using PUCCH format 1, for example, ifthe transmission is during, greater than, or over 4 or more symbols andthe number of HARQ-ACK/SR bits is 1 or 2. The wireless device maytransmit UCI in a PUCCH using PUCCH format 2, for example, if thetransmission is during, greater than, or over 1 symbol or 2 symbols andthe number of UCI bits is more than 2. The wireless device may transmitUCI in a PUCCH using PUCCH format 3, for example, if the transmission isduring, greater than, or over 4 or more symbols, the quantity of UCIbits is more than 2 and a PUCCH resource does not include an orthogonalcover code. The wireless device may transmit UCI in a PUCCH using PUCCHformat 4, for example, if the transmission is during, greater than, orover 4 or more symbols, the quantity of UCI bits is more than 2 and thePUCCH resource includes an orthogonal cover code.

A wireless device may determine a PUCCH resource from a PUCCH resourceset, for example, to transmit HARQ-ACK information on the PUCCHresource. The PUCCH resource set may be determined as described herein.The wireless device may determine the PUCCH resource based on a PUCCHresource indicator field in DCI (e.g., with a DCI format 1_0 or DCI for1_1) received on a PDCCH. A PUCCH resource indicator field in the DCImay indicate one of eight PUCCH resources in the PUCCH resource set. Thewireless device may transmit the HARQ-ACK information in a PUCCHresource indicated by the PUCCH resource indicator field in the DCI. ThePUCCH resource indicator field may be 3-bits (e.g., or any otherquantity of bits) in length.

The wireless device may transmit one or more UCI bits via a PUCCHresource of an active uplink BWP of a PCell or a PUCCH secondary cell.The PUCCH resource indicated in the DCI may be a PUCCH resource on theactive uplink BWP of the cell, for example, if at most one active UL BWPin a cell is supported for a wireless device.

AA wireless device may perform various operations to improve wirelessdevice power consumption efficiency and/or increase battery lifetime.Wireless devices may save power in a variety of ways, including, forexample, by not transmitting/receiving via one or more channelresources, turning off antennas, turning off receiving modules, etc. Forexample, a wireless device may monitor channels and/or receive signalsdiscontinuously, in time, using DRX operation.

A wireless device may discontinuously monitor downlink control channel(e.g., PDCCH or enhanced EPDCCH)) during DRX operation. A base stationmay configure DRX operation (e.g., via RRC configuration messages) witha set of DRX parameters. The set of DRX parameters may be selected basedon an application type such that the wireless device may reduce powerand resource consumption. A wireless device may receive data packetswith an extended delay, for example, if DRX is configured/activated, Thedelay may be because the wireless device may be in DRX sleep/OFF stateat the time of data arrival at the wireless device and the base stationmay have to wait until the wireless device transitions to the DRX ONstate.

The wireless device may power down most of its circuitry if there are nopackets to be received, for example, if the wireless device is operatingin a DRX mode. The wireless device may monitor PDCCH discontinuously inthe DRX mode. The wireless device may monitor the PDCCH continuously ifa DRX operation is not configured. The wireless device may listento/monitor downlink (DL) channels (e.g., PDCCHs), for example, if a DRXoperation is not configured or if the wireless device is in a DRX activestate. A wireless device may not listen to/monitor DL channels (e.g.,PDCCHs), for example, if a wireless device is in DRX mode of operationand in a DRX leep state.

A base station may send/transmit an RRC message comprising one or moreDRX parameters of a DRX cycle. The one or more parameters may comprise afirst parameter and/or a second parameter. The first parameter mayindicate a first time value of the DRX active state (e.g., DRX ONduration) of the DRX cycle. The second parameter may indicate a secondtime value of the DRX sleep state (e.g., DRX OFF duration) of the DRXcycle. The one or more parameters may further comprise a time durationof the DRX cycle. The wireless device may monitor PDCCHs for detectingone or more DCIs on a serving cell, for example, if the wireless deviceis in a DRX active state. The wireless device may stop monitoring PDCCHson the serving cell, for example, if the wireless device is in a DRXsleep state. The wireless device, in a DRX active state, may monitor allPDCCHs on (or for) multiple cells, for example, if multiple cells are inactive state. The wireless device may stop monitoring all PDCCHs on (orfor) the multiple cells, for example, during the DRX OFF duration. Thewireless device may repeat the DRX operations according to the one ormore DRX parameters.

DRX may be beneficial for the base station. The wireless device may besending/transmitting periodic CSI reports and/or SRSs frequently (e.g.,based on the configuration), for example, if DRX is not configured. Thewireless device may not transmit periodic CSI and/or SRS in DRX OFFperiods. The base station may assign these resources to the otherwireless devices, for example, to improve resource utilizationefficiency.

A wireless device (e.g., a MAC entity of the wireless device) may beconfigured (e.g., by RRC messaging) with a DRX functionality. The DRXfunctionality may control the wireless device's downlink control channel(e.g., PDCCH) monitoring activity for a plurality of RNTIs. Theplurality of RNTIs may comprise at least one of: C-RNTI, CS-RNTI,INT-RNTI, SP-CSI-RNTI, SFI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI,Semi-Persistent Scheduling C-RNTI, eIMTA-RNTI, SL-RNTI, SL-V-RNTI,CC-RNTI, and/or SRS-TPC-RNTI. The wireless device may monitor the PDCCHdiscontinuously using the DRX operation, for example, if the wirelessdevice is in an RRC connected state (e.g., RRC_CONNECTED) and if DRXoperation is configured. The wireless device may monitor the PDCCHcontinuously, for example, if DRX operation is not configured.

RRC messaging may control DRX operation by configuring a plurality oftimers. The plurality of timers may comprise: a DRX ON duration timer(e.g., drx-onDurationTimer), a DRX inactivity timer (e.g.,drx-InactivityTimer), a downlink DRX HARQ RTT timer (e.g.,drx-HARQ-RTT-TimerDL), an uplink DRX HARQ RTT timer (e.g.,drx-HARQ-RTT-TimerUL), a downlink retransmission timer (e.g.,drx-RetransmissionTimerDL), an uplink retransmission timer (e.g.,drx-RetransmissionTimerUL). RRC messaging may configure one or moreparameters of a short DRX configuration (e.g., drx-ShortCycle and/ordrx-ShortCycleTimer)), and/or one or more parameters of a long DRXconfiguration (e.g., drx-LongCycle). Time granularity for DRX timers maybe configured in terms of PDCCH subframes (e.g., indicated as psf in theDRX configurations), or in terms of milliseconds (or in any other unitsof time).

The active time (e.g., time period in which the wireless device is inDRX active state) may comprise the time period in which at least onetimer is running, for example, if a DRX cycle is configured. The atleast one timer may comprise one or more of a DRX ON duration timer(e.g., drx-onDurationTimer), a DRX inactivity timer (e.g.,drx-InactivityTimer), a downlink retransmission timer (e.g.,drx-RetransmissionTimerDL), an uplink retransmission timer (e.g.,drx-RetransmissionTimerUL), and/or a MAC contention resolution timer(e.g., mac-ContentionResolutionTimer).

The DRX inactivity timer (e.g., drx-Inactivity-Timer) may specify a timeduration for which the wireless device may be active, for example, basedon/after successfully decoding a PDCCH indicating a new transmission (ULor DL or sidelink (SL)). The DRX inactivity timer may be restarted uponreceiving a PDCCH transmission for (e.g., corresponding to, orindicating) a new transmission (UL or DL or SL). The wireless device maytransition to a DRX mode (e.g., using a short DRX cycle or a long DRXcycle), for example, based on/in response to the expiry of the DRXinactivity timer.

Short DRX (e.g., configured by parameter drx-ShortCycle) may be a firsttype of DRX cycle (e.g., if configured) that may be used, for example,based on (e.g., when) the wireless device enters DRX mode. Aninformation element (IE) (e.g., DRX-Config IE) may indicate the lengthof the short cycle. A DRX short cycle timer (e.g., drx-ShortCycleTimer)may be expressed as multiples of a short DRX cycle (e.g.,shortDRX-Cycle). The timer may indicate a quantity of initial short DRXcycles to follow before entering the long DRX cycle.

A DRX ON duration timer (e.g., drx-onDurationTimer) may specify the timeduration at the beginning of a DRX Cycle (e.g., DRX ON). DRX ON durationtimer may indicate the time duration before entering the sleep mode (DRXOFF). A downlink DRX HARQ RTT timer (e.g., drx-HARQ-RTT-TimerDL) mayspecify a minimum duration from a time at which a new transmission isreceived and before the wireless device may expect a retransmission of asame packet. This timer may be fixed and may not be configured by RRC. Adownlink retransmission timer (e.g., drx-RetransmissionTimerDL) mayindicate a maximum duration for which a wireless device may monitor aPDCCH for a retransmission from a base station (e.g., eNodeB).

The active Time may comprise the time in which a scheduling request issent via a PUCCH and is pending, for example, if the DRX cycle isconfigured. The active time may comprise the time in which an uplinkgrant for a pending HARQ retransmission may occur and there is data inthe corresponding HARQ buffer for synchronous HARQ process, for example,if the DRX cycle is configured. The active time may comprise the time inwhich a PDCCH transmission indicating a new transmission addressed tothe C-RNTI of the MAC entity has not been received after successfulreception of a random access response for the preamble not selected bythe MAC entity, for example, if the DRX cycle is configured.

DRX may be configured for a wireless device. A DL HARQ RTT timer mayexpire in a subframe/slot and the data of the corresponding HARQ processmay not be successfully decoded. The wireless device may start thedownlink retransmission timer (e.g., drx-RetransmissionTimerDL) for thecorresponding HARQ process, for example, if the DL HARQ RTT timerexpires in a subframe/slot and the data of the corresponding HARQprocess is not successfully decoded.

An UL HARQ RTT timer may expire in a subframe/slot. The wireless devicemay start the uplink retransmission timer (e.g.,drx-RetransmissionTimerUL) for the corresponding HARQ process, forexample, if the UL HARQ RTT timer expires.

A DRX command MAC control element or a long DRX command MAC controlelement may be received (e.g., by the wireless device). The wirelessdevice may stop the DRX ON duration timer (e.g., drx-onDurationTimer)and stop the DRX inactivity timer (e.g., drx-InactivityTimer), forexample, if the wireless device receives a DRX command MAC controlelement or a long DRX command MAC control element.

The DRX inactivity timer (e.g., drx-InactivityTimer) may expire or a DRXcommand MAC control element may be received in a subframe. The wirelessdevice, configured with a short DRX cycle, may start or restart the DRXshort cycle timer (e.g., drx-ShortCycleTimer) and may use the short DRXcycle, for example, if the DRX inactivity timer expires or if the DRXcommand MAC control element is received. Otherwise, the wireless devicemay use the long DRX cycle.

The DRX short cycle timer (e.g., drx-ShortCycleTimer) may expire in asubframe. The wireless device may use the long DRX cycle, for example,if the DRX short cycle timer expires in the subframe. The wirelessdevice may receive a long DRX command MAC control element may bereceived. The wireless device may stop the DRX short cycle timer (e.g.,drx-ShortCycleTimer) and/or may use the long DRX cycle, for example, ifthe wireless device receives a long DRX command MAC control element.

The wireless device may start the DRX ON duration timer (e.g.,drx-onDurationTimer), for example, if the short DRX Cycle is used and if[(SFN*10)+subframe number] modulo (drx-ShortCycle)=(drxStartOffset)modulo (drx-ShortCycle). The wireless device may start the DRX ONduration timer (e.g., drx-onDurationTimer), for example, if the long DRXCycle is used and [(SFN*10)+subframe number] modulo(drx-longCycle)=drxStartOffset.

A wireless device may be served by a plurality of cells (e.g., a primarycell and one or more secondary cells). A base station may send controlsignals (e.g., PDCCH transmissions) to the wireless device to scheduledownlink/uplink transmissions. Each cell may be associated with one ormore common search spaces and/or one or more wireless-device specificsearch spaces. The wireless device may monitor the search spaces toreceive control signals (e.g., DCI) from the base station. For example,the common search spaces may be monitored for receiving controlinformation associated with SIB transmissions, random access processes,RRC reconfiguration, etc. The common search spaces may be monitored forreceiving group-common DCI (e.g., comprising slot format indicator,transmission power control information (TPC), pre-emption indication,etc.). The wireless device-specific search spaces may be monitored forreceiving control information associated with dedicated data scheduling(e.g., downlink/uplink grants).

Uplink/downlink transmissions on a cell may be scheduled via the samecell (e.g., self-carrier scheduling) or via a different cell (e.g.,cross-carrier scheduling). For example, uplink/downlink transmissionsmay be scheduled on a cell based on control signals sent via controlchannels associated with the cell (e.g., self-carrier scheduling) and/orbased on control signals sent via control channels associated with adifferent cell (e.g., cross-carrier scheduling), also known as ascheduling cell.

Cross-carrier scheduling of a cell may enable reduced resourceutilization on the cell. For example, the cell may be associated withresources that may be shared by different types of communications (e.g.,associated with a fourth generation communications standard, such asLTE; a fifth generation standard, such as NR or NR-unlicensed; a 6thgeneration standard; or any nth generation standard). A scheduling cellmay be associated with a communication type that enables increasedchannel capacity (e.g., a fifth generation standard operating at higherfrequencies). Scheduling resources on the cell based on controlsignaling sent via the scheduling cell (e.g., cross-carrier scheduling)may reduce resource utilization and improve reliability at the cell. Asfurther described herein, cross-carrier scheduling for the cell may leadto issues for certain wireless communication procedures (e.g., randomaccess procedures used for initial access and beam failure recovery,fallback DCI transmission, etc.).

A base station may configure one or more parameters for a cross-carrierscheduling for a first cell. The one or more parameters may comprise ascheduling cell indicator/index. A wireless device may activate thecross-carrier scheduling for the first cell, for example, based on(e.g., in response to) receiving the one or more parameters for thecross-carrier scheduling. The scheduling cell may indicate (and/or maybe used for scheduling) one or more control messages (e.g., DCIs)comprising resource assignments for the first cell. The wireless devicemay not monitor any search space via the first cell, for example, if thefirst cell is configured with the cross-carrier scheduling. The wirelessdevice may not monitor any CORESET on the first cell, for example, ifcross-carrier scheduling is enabled.

Disabling monitoring any CORESET on a primary cell, configured withcross-carrier scheduling, may lead to an inefficient initial accessprocedure (e.g., a random access procedure). The base station mayconfigure resources (e.g., PRACH resources) in an initial UL BWP of theprimary cell. The base station may send an RAR based on receiving aPRACH transmission. The base station may configure one or more searchspaces, in an initial DL BWP of the primary cell, for RAR reception. Thebase station may configure one or more second search spaces, on ascheduling cell for the primary cell, for RAR reception, for example, ifcross-carrier scheduling is enabled for the primary cell. RAR may bemultiplexed among a plurality of wireless devices, wherein a firstwireless device of the plurality of the wireless devices may operateusing self-carrier scheduling of the primary cell and a second wirelessdevice of the plurality of wireless devices may operate usingcross-carrier scheduling for the primary cell. The base station maydetermine to or need to send first DCI via the primary cell, and secondDCI via the scheduling cell, as the base station may not know whetherthe first wireless device and/or the second wireless device may havesent the PRACH transmission. Sending DCIs via both the primary cell andthe scheduling cell may be inefficient and/or may result in increasedresource utilization.

A wireless device may monitor one or more search spaces of a schedulingcell for receiving downlink/uplink scheduling. The wireless device maymonitor one or more search spaces of a scheduling cell for receivingdownlink/uplink scheduling, for example, DCIs, for example, if thewireless device is configured with cross-carrier scheduling for a cell(e.g., different from the scheduling cell). The wireless device maytrigger a random access procedure for the cell (e.g., for a beam failurerecovery of the wireless device for a beam failure detected on thecell). The wireless device may receive a RAR (e.g., Msg 2 1312 asdescribed with reference to FIG. 13A, or Msg 2 1322 as described withreference to FIG. 13B) via a scheduling cell different from the cell.The wireless device may determine a new beam based on the received RAR.The wireless device may not be able to accurately determine the newbeam, for example, if the wireless device receives the RAR via thescheduling cell for a random access procedure triggered for the cell.The new beam may not be a best beam for the wireless device because thewireless device may have detected the beam failure on the cell and thenew beam may be associated with an RAR received via the scheduling cell.

A base station may send/transmit, via a common search space, fallbackDCI scheduling data for RRC reconfiguration (e.g., for reconfiguring ascheduling cell for a primary cell). The base station may send/transmitthe fallback DCI via a scheduling cell, for example, if cross-carrierscheduling is configured for the primary cell. The base station maytransmit the fallback DCI via the scheduling cell, where a link qualityof the scheduling cell may be poor. The wireless device may perform aradio link monitoring for the primary cell and may not perform a radiolink monitoring for the scheduling cell. The base station may not beaware of the link quality of the scheduling cell (e.g., which may havepoor radio link quality) and/or the base station may not be able tosuccessfully transmit (and/or the wireless device may not successfullyreceive) the fallback DCI. The wireless device may not trigger a radiolink failure if the link quality of the primary cell is good. Nottriggering a radio link failure may lead to failure of RRCreconfiguration and/or increase a latency in RRC reconfiguration.

A wireless device may monitor one or more search spaces of a firstscheduling cell for receiving downlink/uplink scheduling DCIs, forexample, if the wireless device is configured with cross-carrierscheduling for a primary cell (e.g., different from the first schedulingcell). Cross-carrier scheduling may need to be reconfigured to a secondscheduling cell, for example, if channel conditions associated with thefirst scheduling cell are poor. Poor channel conditions at the firstscheduling cell, for example, during a time period at which thereconfiguration occurs, may result in the base station being unable toefficiently schedule transmissions via the primary cell.

A wireless device may need additional capabilities to support monitoringone or more common search spaces of a secondary cell for scheduling data(e.g., RAR messages, SIB messages, and/or RRC messages messages) for aprimary cell. The secondary cell may be a scheduling cell for theprimary cell for cross-carrier scheduling. Cross-carrier scheduling forthe primary cell may result in increased complexity at the wirelessdevice in such scenarios. Described herein are example enhancements forsupporting cross-carrier scheduling.

A wireless device may be configured with cross-carrier scheduling for aprimary cell. The wireless device may be configured with self-carrierscheduling for the primary cell. The wireless device may useself-carrier scheduling and/or cross-carrier scheduling for the primarycell, for example, based on one or more considerations as describedherein.

A wireless device may use self-carrier scheduling for one or more firstsearch spaces in a BWP of a first cell. The wireless device may usecross-carrier scheduling for one or more second search spaces of the BWPof the first cell. The one or more first search spaces may becell-specific/common search spaces which may be shared among a pluralityof wireless devices. The one or more first search spaces may beconfigured via one or more SIB messages, MIB messages, and/or RRCmessages. The one or more second search spaces may be wirelessdevice-specific (e.g., UE-specific) search spaces which may be dedicatedto the wireless device. The one or more second search spaces may beconfigured via one or more RRC messages. The wireless device maymaintain performance metrics for receiving one or more broadcastmessages (e.g., RARs, SIBs, paging messages) and may increase controlchannel capacity for receiving one or more unicast messages, forexample, by allowing mixed self-carrier and cross-carrier schedulingamong a plurality of search spaces for a primary cell.

A base station may configure cross-carrier scheduling for a primarycell. Cross-carrier scheduling for the primary cell may increasecapacity of control channels if a scheduling cell for the cross-carrierscheduling has more available resources (e.g., operates at a higherfrequency band). The wireless device may maintain one or more commonsearch spaces via self-carrier scheduling on the primary cell. Thewireless device may maintain one or more wireless device-specific searchspaces via cross-carrier scheduling on the scheduling cell. Maintainingone or more common search spaces via self-carrier scheduling on theprimary cell may allow the wireless device to receive control signals(e.g., DCIs) scheduling messages associated with certain procedures(e.g., RAR corresponding to a PRACH transmission, as triggered based ona beam failure recovery, an initial access procedure, etc.) on theprimary cell. A base station need not configure PRACH resources in thescheduling cell, thereby reducing channel usage. Scheduling RARs,associated with a beam failure recovery procedure on the primary cell,via the primary cell may enable successful beam failure recovery forbeam failures detected on the primary cell. Scheduling RARs associatedwith an initial access procedure only via the primary cell may enablethe base station to skip transmission of RARs via the scheduling cell,reducing channel utilization on the scheduling cell. Various examplesdescribed herein may reduce complexity of the wireless device and enablea random access procedure to be used for a beam failure recoveryprocedure. The wireless device may determine that a candidate beam usedin a preamble is confirmed by DCI scheduling the RAR, for example, basedon receiving the DCI. The wireless device may determine that the beamfailure recovery procedure is completed based on the confirming thecandidate beam. Maintaining common search spaces via self-carrierscheduling on the primary cell and wireless device-specific searchspaces via cross-carrier scheduling on the scheduling cell may allowefficient fallback mechanisms between the base station and the wirelessdevice, for example, if the wireless device experiences poor linkquality in the scheduling cell or the scheduling cell experiences a beamfailure.

The wireless device may use self-carrier scheduling for a primary cell,for example, if an active BWP is an initial BWP. The wireless device maybe able to fallback to a reliable operation of the self-carrierscheduling by disabling the cross-carrier scheduling of the initial BWP.The wireless device may use self-carrier scheduling, for example, if ascheduling cell of the primary cell is not active. The wireless devicemay use self-carrier scheduling, for example, if the wireless deviceswitches to the initial BWP to trigger a PRACH transmission.

Various examples described herein may enable efficient handling ofcommon search spaces and/or improved control channel capacity ofwireless device-specific search spaces for a primary cell. Flexibleconfiguration of mixed self-carrier and cross-carrier scheduling may beprovided. A fallback operation of self-carrier scheduling for theprimary cell may be provided, for example, wherein the wireless devicemay switch back to the self-carrier scheduling (e.g., if an active BWPis an initial BWP).

A base station may configure a wireless device with cross-carrierscheduling for a first cell. The base station may configure a secondcell to be a scheduling cell for the first cell. The wireless device mayapply cross-carrier scheduling for the first cell, for example, based onthe cross-carrier scheduling configuration. The base station mayconfigure a plurality of BWPs for the first cell. The plurality of BWPsmay comprise an initial BWP and a BWP. The plurality of BWPs maycomprise a default BWP. The plurality of BWPs may comprise a dormantBWP. The plurality of BWPs may comprise a power-saving BWP.

Cross-carrier scheduling may be configured as a cell-level configurationparameter. The cross-carrier scheduling may be applied for each BWP ofthe plurality of BWPs of the first cell, for example, if the first cellis configured with cross-carrier scheduling. The wireless device mayapply cross-carrier scheduling to an active BWP of the first cell,regardless of which BWP, among the plurality of BWPs, is the active BWP.Applying cross-carrier scheduling for each of the plurality of BWPs ofthe first cell may lead to inefficiencies (e.g., performancedegradation, higher power consumption, etc.) in at least certainscenarios. A first BWP of the plurality of BWPs of the first cell may bea default BWP or an initial BWP or may have a small bandwidth for powersaving mode operation. A second BWP of the plurality of BWPs of thefirst cell may have a large/full bandwidth for active traffic. Enablingcross-carrier scheduling for the second BWP may be advantageous forincreasing control signaling capability and reducing overhead at thefirst cell. However, enabling cross-carrier scheduling for the first BWPmay be inefficient (e.g., may increase power consumption). For example,an active BWP of the scheduling cell may have a large/full bandwidth,and a search space of the active BWP of the scheduling cell may havelarge quantity of control channel candidates. The wireless device mayconsume more power to monitor a large number/quantity of control channelcandidates for the first cell, even though the first cell may be inpower saving state and the first BWP may have a small bandwidth.

Applying cross-carrier scheduling for each of the plurality of BWPs ofthe first cell may impose restrictions on transitioning of cells (e.g.,from an active state to a dormant state). For example, the base stationmay be triggered to transition the second cell (e.g., a scheduling cell)to a dormant state and transition to the default BWP, of the first cell,with low traffic for the wireless device. The base station may not beable to transition the second cell to the dormant state, for example, ifcross-carrier scheduling is enabled for the first cell (e.g., and thedefault BWP of the first cell).

Applying cross-carrier scheduling for each of the plurality of BWPs ofthe first cell may not account for variations in channel qualities amongthe plurality of BWPs. Better efficiency of scheduling may be achievedbased on self-carrier scheduling or cross-carrier scheduling, forexample, if BWPs are individually configured with self-carrierscheduling and cross-carrier scheduling based on channel qualities. Forexample, self-carrier scheduling of a BWP may be beneficial, forexample, if a channel quality of the second cell is low. Cross-carrierscheduling of a BWP may be beneficial, for example, if a channel qualityof the second cell is high.

Various examples described herein may configure self-carrier schedulingor cross-carrier scheduling on a per-BWP basis for BWPs of a cell. Abase station may configure self-carrier scheduling or a cross-carrierscheduling for each BWP of one or more BWPs of a cell. The base stationmay configure one or more parameters of cross-carrier scheduling viacell-level configuration (e.g., using higher layer parameterCrossCarrierScheduling). The base station may furtherindicate/configure, for each BWP of the one or more BWPs, self-carrierscheduling or the cross-carrier scheduling. Self-carrier scheduling orcross-carrier scheduling for each BWP may be implicitly or explicitlyindicated.

The base station may indicate self-carrier scheduling or cross-carrierscheduling for each BWP based on configuration of one or more CORESETs.The base station may not configure one or more first CORESETs,associated with one or more search spaces of the cell, for a first BWPof the cell, for example, to enable cross-carrier scheduling for thefirst BWP. The base station may configure one or more second CORESETs,associated with the one or more search spaces of the cell, for a secondBWP of the cell, for example, to enable self-carrier scheduling for thesecond BWP. The one or more search spaces may be wirelessdevice-specific search spaces. The base station may indicateself-carrier scheduling or cross-carrier scheduling for each BWP basedon explicit indication. The wireless device may determine (e.g., basedon CORESET configuration or based on explicit indication), self-carrierscheduling for one or more BWPs (e.g., dormant BWP, initial BWP, defaultBWP). The wireless device may determine (e.g., based on CORESETconfiguration or based on explicit indication) cross-carrier schedulingfor one or more other BWPs (e.g., non-dormant BWP, non-initial BWP,non-default BWP).

A base station may configure one or more first BWPs of a first cell. Theone or more first BWPs may be configured/indicated with self-carrierscheduling by the first cell. The base station may configure one or moresecond BWPs of the first cell. The one or more second BWPs may beconfigured/indicated with a cross-carrier scheduling by a second cell.The base station may enable cross-carrier scheduling by the first cell,for example, based on indicating switching of an active BWP of the firstcell from a first BWP of the one or more first BWPs to a second BWP ofthe one or more second BWPs. The base station may disable cross-carrierscheduling and/or switch to the self-carrier scheduling, for example,based on indicating switching of the active BWP of the first cell fromthe second BWP of the one or more second BWPs to the first BWP of theone or more first BWPs. The base station may be able to dynamicallyenable or disable cross-carrier scheduling for the first cell based onBWP switching framework. Dynamically enabling and disabling ofcross-carrier scheduling based on BWP switching framework isadvantageous if applied for a primary cell of a cell group or a PUCCHgroup, where reliability and control channel performance arecontinuously measured (e.g., radio link monitoring for checking liveconnection with the base station) to handle wireless device mobility.Dynamically enabling and disabling of cross-carrier scheduling based onBWP switching framework may reduce overhead associated with enabling ordisabling cross-carrier scheduling.

A wireless device may support up to K BWPs for a cell and M searchspaces for the cell (e.g., K=4, or any other quantity, and M=20, or anyother quantity). Using BWP switching for enabling/disablingcross-carrier scheduling for the cell, as described above, may encounterlimitations if a quantity of BWPs is high. The wireless device may beconfigured with an initial BWP and a default BWP on a primary cell of acell group. The wireless device may need to support different schedulingoptions (e.g., self-carrier scheduling and cross-carrier scheduling)based on the remaining quantity BWPs (e.g., K-2 BWPs). A quantity ofBWPs K may need to may need to be increased to support the differentscheduling options. A signaling overhead (e.g., a quantity of bitsrequired in DCI) to indicate BWP switching may increase, for example, ifa quantity of BWPs is increased. For example, the quantity of bits inDCI to indicate BWP switching may be log 2(K).

Various examples described herein enable signaling of BWPs (e.g., forBWP switching) with reduced overhead even if a quantity of BWPs isincreased to accommodate different types of scheduling configurations. Abase station may configure a first BWP group for a first cell. The firstBWP group may comprise one or more first BWPs configured/associated withself-carrier scheduling. The base station may configure a second BWPgroup for the first cell. The second BWP group may comprise one or moresecond BWPs configured/associated with cross-carrier scheduling by asecond cell. The base station may switch, based on BWP switching DCI,from a first BWP within a group to a second BWP within the same group. Aquantity of bits in DCI for BWP switching may be limited to a quantityof BWPs of the group. The base station and the wireless device mayswitch between the first BWP group and the second BWP group based on oneor more rules and/or one or more indications. For example, the wirelessdevice may switch to the second BWP group, for example, based on/inresponse to receiving an activation of the second cell. The base stationmay send/transmit a DCI field indicating the first BWP group or thesecond BWP group for the first cell. The DCI may be scheduling DCI ordedicated non-scheduling DCI.

Various examples described herein may allow dynamic enabling/disablingof cross-carrier scheduling for a cell with a low overhead (e.g., DCIoverhead, wireless device capability, and/or the like). Flexibility ofscheduling for a cell may be provided, for example, with a base stationutilizing different scheduling mechanisms or a different set of searchspaces based on an active BWP of the cell.

A wireless device may receive (e.g., from a base station) one or moresystem information blocks (SIBs) for a cell via one or more searchspaces (e.g., search space #0 and/or a search space #1) of the cell. Thewireless device may receive one or more DCIs comprising resourceassignments for scheduling PDSCH transmissions. The PDSCH transmissionsmay comprise the one or more SIBs.

The wireless device may send a PRACH transmission for accessing the cell(e.g., associating with the cell), for example, based on the one or moreSIBs of the cell. A base station may send/transmit a RAR, for example,based on/in response to receiving the PRACH transmission. The basestation may send/transmit DCI, via a first search space of the cell(e.g., the search space #1 or a search space #2), comprising resourceassignments for a PDSCH transmission (e.g., comprising the RAR). Thewireless device may send a PUSCH transmission (e.g., Msg 3, similar toMsg 3 1313 as described with reference to FIG. 13A), for example, basedon/in response to receiving the RAR. The wireless device may monitor, asecond search space of the cell (e.g., the search space #1 or the searchspace #2), for one or more DCIs scheduling PDSCHs (e.g., comprising Msg4, similar to Msg 4 1314, and/or RRC configurations). The wirelessdevice may monitor, for the random access procedure, one or more DCIsscheduling downlink/uplink data reception/transmissions via one or moresearch spaces of the cell that the wireless device attempts to beassociated with.

A wireless device may perform a random access procedure initially on aninitial DL BWP and/or an initial UL BWP of a cell. The wireless devicemay monitor the first search space and the second search space of thecell on the initial DL BWP. The initial DL BWP may be an initial activeDL BWP. The wireless device may send a PRACH transmission via theinitial UL BWP of the cell. The initial UL BWP may be an initial activeUL BWP. The wireless device may switch to a DL BWP and/or a UL BWP fromthe initial DL/UL BWP. The wireless device may switch back to theinitial DL/UL BWP of the cell, for example, if the wireless device isnot configured with RACH resources in an active DL/UL BWP of the cell.

The wireless device may be associated with a first DL BWP and a first ULBWP as an active DL/UL BWP of the cell. The first DL BWP and the firstUL BWP may be the same or different from the initial DL BWP and theinitial UL BWP. The base station may configure cross-carrier schedulingfor the cell. A wireless device may or may not apply the cross-carrierscheduling, for example, if the active DL BWP is the initial DL BWP ofthe cell. The wireless device may disable one or more configurationparameters for the cross-carrier scheduling and may switch back toself-carrier scheduling for the cell, for example, if the current activeDL BWP is the initial DL BWP. The wireless device may monitor the firstsearch space and/or the second search space of the cell on the initialDL BWP regardless of whether the wireless device is configured withcross-carrier scheduling for the cell or self-carrier scheduling for thecell. The wireless device may monitor the first search space and/or thesecond search space, for example, only if the wireless device may havesent one or more PRACH transmissions via the cell. A wireless device maybe configured with PRACH configurations to support four-step andtwo-step random access procedures on a cell. The wireless device maymonitor one or more search spaces of the cell for one or more DCIsscheduling one or more messages (e.g., response messages for thefour-step based PRACH transmission or the two-step based PRACHtransmission, based on the type of the selected random accessprocedure). The wireless device may monitor DCIs for the random accessprocedure on the cell (e.g., regardless of the type of the selectedrandom access procedure), for example, if a PRACH transmission has beensent via the cell.

A wireless device may monitor one or more first search spaces of a firstBWP of a first cell. The wireless device may receive one or more firstDCIs, comprising resource assignments for downlink/uplink transmissionfor the first cell, via the one or more first search spaces. Thewireless device may monitor one or more second search spaces of a secondBWP of a second cell. The wireless device may receive one or more secondDCIs, comprising resource assignments for downlink/uplink transmissionfor the first cell, via the one or more second search spaces. The one ormore first search spaces may comprise one or more common search spacesconfigured/associated with the first cell. The one or more second searchspaces of the second cell may comprise one or more wirelessdevice-specific search spaces configured for cross-carrier schedulingthe first cell. The one or more first search spaces may comprise one ormore first common search spaces and/or one or more first wirelessdevice-specific search spaces. The one or more second search spaces maycomprise one or more second common search spaces and/or one or moresecond wireless device-specific search spaces.

The one or more first search spaces may comprise a search space for thefirst cell. The wireless device may monitor the search space for DCIsscheduling paging. The wireless device may monitor the search space forDCIs scheduling a RAR. The wireless device may monitor the search spacefor DCIs scheduling a message (e.g., Msg 4 and/or a RAR message for atwo-step RACH procedure (Msg B), and/or DCIs scheduling PDSCHtransmissions comprising RRC (re)configuration messages. The wirelessdevice may monitor the search space for DCIs scheduling SIBs. Thewireless device may monitor the search space for fallback DCIs (e.g.,DCI transmitted via a PDCCH based on a fallback DCI format such as DCIformat 0_0/1_0) scheduling data. The one or more search spaces maycomprise a second search space, of the second cell, for schedulingtransmissions in the first cell. The wireless device may monitor thesecond search space of the second cell for non-fallback DCIs (e.g., DCItransmitted via a PDCCH based on a non-fallback DCI format such as DCIformat 0_1/1_1) scheduling data for the first cell.

A base station may configure a cell indicator/index corresponding to asearch space. The cell indicator/index may indicate a same cell in whichthe search space is configured or may indicate a cell different from thecell in which the search space is configured. The wireless device maymonitor the search space on the cell via self-carrier scheduling, forexample, if the same cell is indicated. The wireless device may monitorthe search space on the indicated cell, different from the cell, via across-carrier scheduling, for example, if the different cell isindicated.

Various examples described herein may allow flexible configuration for aprimary cell of a cell group and/or a PUCCH SCell of a cell group.Self-carrier scheduling of such a cell of the cell group (e.g., primarycell of a master cell group, primary cell of a secondary cell group, orPUCCH SCell of a PUCCH cell group) may be beneficial as the primary cellmay always active and may be configured to a frequency which shows agood channel quality. Cross-carrier scheduling for the cell may bebeneficial as the primary cell may not have sufficient resources forcontrol channel transmissions. A BWP (or any other wireless resource,frequency range, etc.) of the cell may comprise search spaces associatedwith both self-carrier scheduling and cross-carrier scheduling in orderto achieve benefits of both self-carrier and cross-carrier scheduling.The BWP of the cell may comprise one or more first search spacesassociated with self-carrier scheduling. The BWP of the cell may alsocomprise one or more second search spaces associated with thecross-carrier scheduling. Using self-carrier scheduling for one or morecommon search spaces may improve resource utilization. For example, thebase station may send a shared control/data channel transmission via thesame cell to a plurality of wireless devices. The base station maymaintain one or more first frequencies as candidate cells for a primarycell for a wireless device. The base station may maintain one or moresecond frequencies as candidate cells for a second cell for the wirelessdevice. The base station may not send/transmit SIBs/RARs via the one ormore second frequencies as the one or more second frequencies may beused as the secondary cells. It may be beneficial to keep common searchspaces of a primary cell on the primary cell (e.g., use self-carrierscheduling), for example, even if a cell from the one or more secondfrequencies may schedule for the primary cell for the wireless device.Keeping the common search spaces of the primary cell on the primary cellmay enable the base station to not be required to additionally transmitcontrol/data via other common search spaces of a scheduling cell.

A wireless device may receive one or more messages. The one or moremessages may comprise a MIB, a SIB, and/or RRC messages. The one or moremessages may comprise configuration parameters for a first cell. Thefirst cell may be a primary cell of a cell group (e.g., PCell for afirst cell group, PSCell for a second cell group, a PUCCH cell for aPUCCH group). The configuration parameters may comprise one or moreparameters for cross-carrier scheduling. The one or more parameters forthe cross-carrier scheduling may comprise a scheduling cellindicator/index for the first cell, for example, if the cross-carrierscheduling is enabled. The one or more parameters for the cross-carrierscheduling may comprise a carrier index field (CIF) used for the firstcell, for example, if the cross-carrier scheduling is enabled. Theconfiguration parameters may comprise a first DL BWP and a seconddownlink BWP. The first DL BWP may be configured via MIB transmission.The first DL BWP may be a first active DL BWP of the first cell, forexample, if the first cell is a secondary cell. The first DL BWP may bea default DL BWP that may be activated/used following an expiration of aBWP inactivity timer of the first cell. The second DL BWP may bedifferent from the first DL BWP. The first DL BWP may be a dormant BWP.The second DL BWP may be a non-dormant BWP. The second DL BWP may not bethe initial DL BWP. The second DL BWP may not be the default DL BWP.

The wireless device may activate the first DL BWP of the first cell asan active DL BWP of the first cell. The wireless device may activate thefirst DL BWP via an initial access to the first cell. The wirelessdevice may activate the first DL BWP, for example, based on/in responseto triggering a PRACH transmission. The wireless device may activate thefirst DL BWP, for example, based on/in response to an expiration of theBWP inactivity timer of the first cell. The wireless device may activatethe first DL BWP based on receiving DCI indicating a BWP switching tothe first DL BWP. The wireless device may apply a self-carrierscheduling, for example, based on/in response to the activating thefirst DL BWP as the active DL BWP. The wireless device may not apply theone or more parameters for the cross-carrier scheduling for the firstcell if the active DL BWP is the first DL BWP, or if the active DL BWPis the initial DL BWP of the first cell, or if the active DL BWP is thedefault DL BWP of the first cell. The wireless device may monitor one ormore first search spaces of the first cell for receiving first DCIscomprising resource assignments for the first cell, for example, basedon applying the self-carrier scheduling.

The wireless device may receive a command to switch to the second DL BWPas the active DL BWP of the first cell. The command may be DCIindicating the BWP switching. The command may be DCI indicatingtransitioning to a non-dormant state for the first cell. The command maybe DCI indicating waking-up the first cell from a DRX OFF state. Thewireless device may apply the one or more parameters for thecross-carrier scheduling for the first cell, for example, based on/inresponse to receiving the command. The wireless device may monitor oneor more second search spaces of the scheduling cell for receiving secondDCIs comprising resource assignments for the first cell.

The wireless device may monitor one or more third search spaces of thefirst cell in addition to the one or more second search spaces of thesecond cell, for example, if the second DL BWP is the active DL BWP ofthe first cell. The one or more third search spaces may becell-specific/common search spaces. The one or more first search spacesmay be common search spaces and/or wireless device-specific searchspaces. The one or more second search spaces may be wirelessdevice-specific search spaces. The wireless device may apply thecross-carrier scheduling for one or more wireless device-specific searchspaces, for example, if the wireless device is configured with thecross-carrier scheduling for the first cell. The wireless device mayapply the self-carrier scheduling for the one or more CSSs. The wirelessdevice may continue monitoring one or more CSSs configured for theactive DL BWP of the first cell regardless of whether the cross-carrierscheduling of the first cell is activated/configured/initiated.

FIG. 21A shows an example random access procedure. The example randomaccess procedure may be a four-step random access procedure (e.g., asdescribed with reference to FIG. 13A) The example random accessprocedure may be for an initial access procedure. The example randomaccess procedure may be for other communication procedures (e.g., beamfailure recovery procedure). FIG. 21B and FIG. 21C show an examplemethod 2130 that may be performed by a base station and an examplemethod 2150 that may be performed by a wireless device, respectively,for the random access procedure. A wireless device 2108 may performself-carrier scheduling, for example, for the random access procedure.The wireless device 2108 may activate an initial DL BWP and/or aninitial UL BWP via the initial access procedure. The wireless device2108 may send/transmit a preamble (e.g., PRACH transmission) and a thirdmessage (e.g., Msg 3 or Msg A) in a two-step random access procedure. Abase station 2104 may send/transmit a RAR and a fourth message (e.g.,Msg 4 or Msg B) based on (e.g., in response to) the preamble and thethird message in the two-step random access procedure.

The base station 2104 may send (e.g., step 2130) one or moreconfiguration messages 2112. The wireless device 2108 may receive (e.g.,step 2152), from the base station 2104, the one or more configurationmessages 2112. The one or more configuration messages 2112 may compriseone or more SIBs and an MIB for a cell. The wireless device 2108 maydetermine an initial DL BWP and an initial UL BWP (e.g., initial DL/UPBWP 2110), for example, based on the MIB and the SIBs. The initial DLBWP of the cell may be defined based on a bandwidth and a numerology ofCORESET #0 (e.g., a CORESET with CORESET index=0) of the cell. The basestation 2104 may configure one or more search spaces for the initial DLBWP via the one or more SIBs. The base station 2104 may transmitconfiguration parameters (e.g., via the one or more SIBs in the one ormore messages 2112) for the random access procedure. The one or moreconfiguration parameters may comprise one or more of RACH occasionconfigurations, a search space (e.g., search space #1) for receiving DCIscheduling a RAR, etc. The search space may be associated with the cell.The wireless device 2108 may determines the initial UL BWP, for example,based on information broadcasted via the one or more SIBs. The initialDL BWP and the initial UL BWP of the cell may be based on acell-specific configuration. A first wireless device of the cell mayshare same configurations to a second wireless device of cell, forexample, if the cell if a primary cell of the first wireless device andthe second wireless device.

The wireless device 2108 may send (e.g., step 2154) a PRACH transmission2116 to initiate a connection/initial access procedure to the basestation 2108. The PRACH transmission 2116 may correspond to a firstmessage (e.g., Msg 1) associated with the four-step random accessprocedure. The base station 2104 may receive (e.g., step 2134) the PRACHtransmission 2116.

The base station 2104 may send (e.g., step 2136), via the search space(e.g., search space #1), first DCI scheduling a second message (e.g., anRAR). The wireless device 2108 may monitor the search space for thefirst DCI. The wireless device 2108 may receive (e.g., step 2156) thefirst DCI via the search space. The wireless device 2108 may monitor thesearch space (e.g., search space #1) for receiving RAR 2120, forexample, based on/in response to sending the PRACH transmission 2116and/or based on the first DCI. The base station 2104 may send (e.g.,step 2138), and the wireless device 2108 may receive (e.g., step 2158),the RAR 2120 via the search space. The RAR 2120 may comprise resourceallocation for a third message (e.g., Msg 3 2124).

The wireless device 2108 may send (e.g., step 2160) the third message2124 (e.g., Msg 3), for example, based on receiving the RAR 2120. Thebase station 2104 may receive (e.g., step 2140) the third message 2124.The third message 3 2124 may be used for contention resolution amongdifferent wireless devices. The base station 2104 may send/transmit(e.g., step 2142) a fourth message 2128 (e.g., Msg 4), for example,based on receiving the third message 2124. The fourth message 4 2128 maycomprise one or more of contention resolution message, RRC configurationparameters, and/or RRC configuration messages. The fourth message 2128may be sent via a PDSCH. The wireless device 2108 may receive, via thesearch space used for scheduling for the RAR 2120 (e.g., search space#1) or a second search space (e.g., search space #2), second DCIscheduling the fourth message 2128. The wireless device 2108 may receivethe second DCI, for example, via a search space different from thesearch space used for receiving the first DCI. The wireless device 2108may receive the second DCI via search space 2 and may receive the firstDCI via search space 1. The wireless device 2108 may connect to the basestation 2104, for example, based on receiving (e.g., step 2162) thefourth message 2128.

FIG. 21D and FIG. 21E show an example method 2170 that may be performedby the base station 2104 and an example method 2108 that may beperformed by the wireless device 2108, respectively, for the randomaccess procedure. Steps 2174-2182 of FIG. 21D may be similar to steps2134-2142, respectively, as described with reference to FIG. 21B. Steps2190-2198 of FIG. 21E may be similar to steps 2154-2162, respectively,as described with reference to FIG. 21C.

An active DL BWP and an active UL BWP of the cell, for the initialaccess procedure, may be the initial DL BWP and the initial UL BWP. Thebase station 2104 may configure, via wireless device-specific RRCsignaling, a second BWP, for example, based on/after the initial accessprocedure. The wireless device 2108 may switch to the second BWP, forexample, based on the wireless device-specific RRC signaling. The basestation 2104 may configure one or more BWPs, for example, based on/afterthe initial access procedure. The base station 2104 may activate a BWP,from the one or more BWPs, via BWP switching DCI. The wireless device2108 may transition to a new BWP for the active BWP, for example, basedon/in response to receiving the BWP switching DCI.

A base station may be able to configure cross-carrier scheduling for awireless device via a wireless device-specific signaling. The basestation may be able to configure cross-carrier scheduling for thewireless device, for example, if the wireless device has connected/setupto the base station (e.g., based on/after receiving the fourthmessage/Msg 4). The initial access procedure may be used if the wirelessdevice switches from an RRC idle (e.g., RRC_IDLE) state to an RRCconnected (e.g., RRC_CONNECTED) state. The initial access procedure maybe used if the wireless device switches from an RRC inactive (e.g.,RRC_INACTIVE) state to the RRC connected state. An initial DL/UL BWP ofa cell may be maintained as an active DL/UL BWP, for example, for/duringthe initial access procedure. The wireless device may use self-carrierscheduling on the initial DL/UL BWP of the cell, for example, at leastfor/during the initial access procedure. Enabling cross-carrierscheduling on the initial DL/UL BWP may require dynamicself/cross-carrier scheduling for the initial DL/UL BWP based on one ormore conditions. The one or more conditions may be an RRC state of thewireless device (e.g., cross-carrier scheduling may be enabled if thewireless device is in an RRC connected state). Dynamicself/cross-carrier scheduling may require configurations of one or morefirst search spaces associated with self-carrier scheduling and one ormore second search spaces associated with a cross-carrier scheduling forthe initial DL BWP. The configurations of the initial DL BWP (e.g.,configuration of search spaces) may be indicated/transmitted via the oneor more SIBs. The configuration of the one or more second search spacesmay not be effectively performed because SIBs may be broadcasted whereascross-carrier scheduling configuration may be a wirelessdevice-dedicated configuration.

The wireless device may perform self-carrier scheduling for a firstcell. The wireless device may receive one or more DCIs via CORESETs ofthe first cell. The one or more DCIs may comprise resource assignmentsfor the first cell, for example, based on the self-carrier scheduling.The wireless device may perform cross-carrier scheduling for the firstcell. The wireless device may receive one or more second DCIs viaCORESETs/search spaces of a scheduling cell, different from the firstcell. The one or more second DCIs may comprise resource assignments forthe first cell, for example, based on the self-carrier scheduling.

A wireless device may receive one or more RRC messages. The one or moreRRC messages may comprise configuration parameters for a first cell. Thefirst cell may be a primary cell of a cell group. The first cell may bea primary cell of a PUCCH group. The first cell may be a primary cell ofa second cell group. The configuration parameters may indicate a firstsearch space. The wireless device may monitor the first search space forreceiving/monitoring DCIs of a PDCCH of the first cell. Theconfiguration parameters may indicate a second search space formonitoring DCIs of PDCCHs of the first cell. The configurationparameters may indicate a third search space for monitoring DCIs ofPDCCHs of a second cell. The configuration parameters may comprise oneor more parameters for cross-carrier scheduling for the first cell. Theone or more parameters may indicate that the second cell is a schedulingcell for the first cell, for example, if cross-carrier scheduling isenabled. The wireless device may monitor the first search space of thefirst cell for first DCI. The first DCI may be scheduling DCI fordownlink data or uplink data of the first cell. The first DCI may bebased on a fallback DCI format (e.g., DCI format 0_0 and DCI format1_0). The first DCI may be group-common DCI. The group-common DCI maycomprise one or more of: slot formation information/slot formatindicator (SFI) (e.g., parameter Slotformatindicator), transmissionpower control (TPC) information (e.g., for PUCCH transmission, PUSCHtransmission, or SRS), and/or pre-emption indication (PI). The firstsearch space may be a search space #0 (e.g., a search space withindicator/index=0) of the first cell. The first search space may be acommon search space. The first search space may be a search space #1(e.g., a search space with index=1) or search space #2. The first searchspace may be for receiving DCIs scheduling SIBs. The first search spacemay be for receiving DCIs scheduling RARs. The first search space may befor receiving DCIs scheduling a message associated with a random accessprocedure (e.g., Msg 4).

The wireless device may monitor the second search space of the firstcell for second DCI, for example, if cross-carrier scheduling is notactivated. The cross-carrier scheduling may be activated via RRCsignaling, MAC-CE, and/or DCI signaling. The second DCI may compriseresource assignments for downlink or uplink data of the first cell. Thesecond search space may be a wireless device-specific search space. Thesecond search space may be configured via RRC signaling. The secondsearch space may be configured for monitoring the second DCI based on anon-fallback DCI format (e.g., DCI format 1_1 and DCI format 0_1).

The wireless device may receive a command indicating switching fromself-carrier scheduling to cross-carrier scheduling for the first cell.The command may be sent/transmitted via RRC signaling, MAC-CE signaling,and/or DCI signaling. The command may be a MAC CE comprising anactivation of the second cell. The wireless device may activate thecross-carrier scheduling for the first cell, for example, based onactivating the second cell. The command may be an explicit indicationvia the RRC signaling, MAC-CE signaling, and/or DCI signaling. Thecommand may be an indication via a scheduling DCI. The scheduling DCImay comprise an indication to disable or enable cross-carrierscheduling. The command may be a first SCell activation/deactivation MACCE. The SCell activation/deactivation MAC CE may comprise an indicationfor activation or deactivation for one or more secondary cells and maycomprise an indication for the activation for the scheduling cellindicated for the cross-carrier scheduling. The wireless device mayreceive one or more RRC messages comprising configuration parameters ofthe scheduling cell (e.g., serving cell configuration of the schedulingcell). The wireless device may consider the one or more RRC messages asthe command, for example, based on activating the scheduling cell and ifthe scheduling cell is a primary cell of a cell group. The command maybe DCI transitioning the scheduling cell to a non-dormant state from adormant state. The wireless device may determine a status of thescheduling cell, for example, based on the command. Determining thestatus may comprise determining whether one or more search spaces of thescheduling cell is being actively monitored (e.g., the scheduling cellis in a non-dormant state, in an active state, in DRX active time,and/or the like). The command may be a MAC CE or DCI comprising anindication of activation of the cross-carrier scheduling for the firstcell. The wireless device may transition the scheduling cell to anon-dormant state, and active state, or DRX active time, for example,based on receiving the command. The wireless device may transition thescheduling cell to the non-dormant state, for example, if the schedulingcell is in a dormant state and based on receiving the command activatingcross-carrier scheduling for the first cell. The wireless device mayactivate the scheduling cell, for example, if the scheduling cell isdeactivated and based on receiving the command. The command may be asecond MAC CE comprising a cell indicator/index of the scheduling cellfor the first cell.

The wireless device may continue monitoring the first search space ofthe first cell for the first DCI, for example, based on receiving thecommand. The wireless device may activate the cross-carrier schedulingfor the first cell, for example, based on receiving the command. Thewireless device may stop (e.g., halt or suspend) monitoring the secondsearch space of the first cell for the second DCI, for example, basedon/in response to the activating the cross-carrier scheduling for thefirst cell. The wireless device may start monitoring the third searchspace of the second cell for third DCI comprising resource assignmentsfor the first cell, for example, based on/in response to the activatingthe cross-carrier scheduling of the first cell. The wireless device maymonitor one or more first common search spaces of the first cell, forexample, even if the wireless device activates cross-carrier schedulingfor the first cell. The wireless device may monitor one or more secondwireless device-specific search spaces of the second cell for resourceassignments for the first cell, for example, based on cross-carrierscheduling for the first cell. The wireless device may monitor one ormore first search spaces of the first cell for resource assignments forthe first cell, for example, even if the wireless device activatescross-carrier scheduling for the first cell. The wireless device maymonitor one or more second search spaces of the second cell (e.g., ascheduling cell for the first cell) for resource assignments for thefirst cell, for example, based on cross-carrier scheduling for the firstcell.

The second cell configured as a scheduling cell for the first cell maybe a secondary cell of a cell group. The cell group may comprise thefirst cell. The first cell may be a primary cell of the cell group. Thecell group may be a cell group in a dual connectivity. The cell groupmay be a PUCCH group in a carrier aggregation scenario. The cell groupmay be a multiple-timing advance group (TAG). The cell group may be agroup of cells indicated with a dormancy or non-dormancy indication byDCI. Cells associated with a same cell group may transition to a dormantstate or a non-dormant state together. The cell group may be a group ofcells configured with a same DRX configuration. The cell group maycomprise one or more cells based on base station configuration.

The wireless device may receive a second command. The second command maybe sent/transmitted via RRC signaling, MAC CE signaling, and/or DCIsignaling. The second command may indicate switching from cross-carrierscheduling for the first cell to self-carrier scheduling for the firstcell. The second command may deactivate cross-carrier scheduling for thefirst cell. The wireless device may stop (e.g., halt or suspend)monitoring the third search space of the second cell for the third DCIfor the first cell, for example, based on receiving the second command.The wireless device may resume (e.g., start or restart) monitoring thesecond search space of the first cell for the second DCI, for example,based on the first cell operating the self-carrier scheduling. Thewireless device may continue monitoring the first search space for thefirst DCI regardless of whether cross-carrier scheduling is used or theself-carrier scheduling is used or regardless of whether cross-carrierscheduling is enabled or disabled.

The second command may be a MAC CE comprising an deactivation of thesecond cell or the scheduling cell of the first cell. The second commandmay be an RRC message indicating removal or deconfiguration of the oneor more parameters.

A base station may indicate enabling or disabling of cross-carrierscheduling for a first cell. The base station may indicate enabling ordisabling of cross-carrier scheduling for a BWP of the first cell. Thebase station may configure one or more parameters related tocross-carrier scheduling for the BWP of the first cell. The base stationmay indicate the enabling or the disabling of cross-carrier schedulingfor the BWP of the first cell via one or more MAC CEs and/or DCIs.

A base station may enable cross-carrier scheduling of a cell for one ormore DL BWPs. The one or more DL BWPs may or may not comprise an initialDL BWP. The wireless device may operate based on self-carrier schedulingon the initial DL BWP and may operate based on cross-carrier schedulingif a BWP, of the one or more DL BWPs, becomes the active DL BWP.Switching between self-carrier and cross-carrier scheduling based onactivation of a BWP may allow flexible adaptation between self-carrierscheduling and cross-carrier scheduling. The base station may switchbetween self-carrier scheduling and cross-carrier via a BWP switchingmechanism.

A wireless device may receive one or more messages. The one or moremessages may comprise configuration parameters for a first cell. Theconfiguration parameters may indicate one or more first DL BWPs of thefirst cell indicated/configured with self-carrier scheduling. Theconfiguration parameters may indicate one or more second DL BWPs of thefirst cell indicated/configured with cross-carrier scheduling and ascheduling cell indicator/index of a scheduling cell for cross-carrierscheduling. The wireless device may activate a first DL BWP of the oneor more first DL BWPs as an active DL BWP of the first cell. The firstDL BWP may be an initial DL BWP. The first DL BWP may be a first activeDL BWP configured for a secondary cell. The first cell may be a primarycell of a cell group (e.g., PCell, PSCell). The first cell is a primarycell of a PUCCH group. The wireless device may use self-carrierscheduling by activating the first DL BWP of the one or more first DLBWPs, regardless of whether cross-carrier scheduling is configured ornot, for example, at least if the first cell is the primary cell of thecell group or the PUCCH group. The wireless device may use self-carrierscheduling with the first DL BWP as the active DL BWP of the first cell,for example, if the scheduling cell for the first cell is not activated.The wireless device use self-carrier scheduling with the first DL BWP asthe active DL BWP of the first cell, for example, if the scheduling cellfor the first cell is in dormant state.

The wireless device may determine a second DL BWP of the one or moresecond DL BWPs based on a first BWP indicator/index of the first DL BWP,for example, based on receiving the command activating cross-carrierscheduling. The command activating cross-carrier scheduling may be acommand indicating switching from the first DL BWP to the second DL BWP.A second BWP indicator/index of the second DL BWP may be the same as thefirst BWP index. The second BWP index of the second DL BWP may be afunction of the first BWP index (e.g., the second BWP index=the firstBWP index+an offset). The second BWP index may be k-th lowest BWP indexamong one or more indices of the one or more second BWPs. The first BWPindex may be the k-th lowest BWP index among one or more indices of theone or more first BWPs. The wireless device may switch to the second DLBWP of the one or more second DL BWPs as the active DL BWP of the firstcell. The wireless device may use cross-carrier scheduling for the firstcell, for example, if the second DL BWP is the active DL BWP.

The second BWP index of the second DL BWP may be associated with thefirst BWP index of the first DL BWP. The base station may configure theassociation between the second DL BWP and the first DL BWP for the firstcell. The wireless device may switch between the first DL BWP and thesecond DL BWP for transitioning between self-carrier scheduling andcross-carrier scheduling. The association may be determined by thewireless device based on BWP indices of the first DL BWP and the secondDL BWP. The association between the first BWP index and the second BWPindex may be configured by the base station.

The wireless device may receive one or more RRC messages. The one ormore RRC messages may comprise parameters of one or more first searchspaces for the first DL BWP. The wireless device may monitor the one ormore first search spaces of the first DL BWP for one or more first DCIsscheduling resource assignments of data for the first cell, for example,based on self-carrier scheduling being used for the first cell. The oneor more RRC messages may comprise second parameters of one or moresecond search spaces for the second DL BWP. The wireless device mayreceive one or more second RRC messages. The one or more second RRCmessages may comprise third parameters of one or more third searchspaces of a third DL BWP of the scheduling cell. The one or more thirdsearch spaces may correspond to the one or more second search spaces ofthe second DL BWP of the first cell, for example, if cross-carrierscheduling is being used for the first cell. The wireless device maymonitor the one or more third search spaces of the second cell for oneor more second DCIs comprising resource assignments of data for thefirst cell, for example, based on cross-carrier scheduling being usedfor the first cell. The wireless device may stop monitoring the one ormore third search spaces of the second cell for the one or more secondDCIs, for example, based on/in response to transitioning fromcross-carrier scheduling to self-carrier scheduling for the first cell.

Various examples herein describe communication devices (e.g., a basestation and/or a wireless device) sending and/or receiving controlmessages (e.g., DCI) via search spaces. Sending and/or receiving controlmessages via search spaces may comprise sending and/or receiving themessages via control channels (e.g., PDCCHs) associated with the searchspaces.

FIG. 22A shows an example of switching between cross-carrier schedulingand self-carrier scheduling. A base station 2204 may activatecross-carrier scheduling for a cell. A wireless device 2208 may continuemonitoring one or more search spaces of the cell even if cross-carrierscheduling is activated. FIG. 22B and FIG. 22C show example methods thatmay be performed by the base station 2204 and the wireless device 2208,respectively, for cross-carrier and self-carrier scheduling.

The base station 2204 may send/transmit (e.g. at step 2232) one or moreconfiguration messages (e.g., RRC messages). The one or moreconfiguration messages may comprise one or more parameters related to across-carrier scheduling (e.g., cross-carrier configuration 2212) for afirst cell (e.g., primary cell, PCell). The wireless device 2208 mayreceive (e.g., at step 2252) the one or more configuration messagescomprising the one or more parameters. The one or more parameters maycomprise a scheduling cell indicator/index of a second cell (e.g.,secondary cell, SCell). The second cell may schedule (e.g., the basestation may send, via the second cell) one or more DCIs for the firstcell, for example, based on cross-carrier scheduling. The wirelessdevice 2208 may assume/use self-carrier scheduling for the first cell,for example, until the wireless device 2208 may receive an indication ofthe cross-carrier scheduling for the first cell. The base station 2204may configure (e.g., via the one or more configuration messages) searchspaces for the first cell and/or the second cell. The base station 2204may configure a first search space (e.g., SS1) of the first cell. TheSS1 may be used for sending/transmitting one or more DCIs schedulingdownlink and/or uplink data for the first cell. The base station maysend (e.g., step 2236), via the SS1, first DCI (e.g., DCI-1 2214).

The wireless device 2208 may receive (e.g., step 2254), via the SS1, theDCI-1 2214 scheduling downlink data. The wireless device 2208 maymonitor the SS1, for example, based on the wireless device 2208 beingactivated with self-carrier scheduling for the first cell. The basestation 2204 may send (e.g., step 2237), via the first cell, downlinkdata 2216 as scheduled by the DCI-1 2214. The wireless device 2208 mayreceive (e.g., step 2256), via the first cell, the downlink data 2216scheduled by the DCI-1 2214.

The base station 2204 may send (e.g., step 2238), to the wireless device2208, a message (e.g., command 2218) to activate cross-carrierscheduling. The wireless device 2208 may activate cross-carrierscheduling for the first cell, for example, based on receiving thecommand 2218. The base station 2204 and/or the wireless device 2208 maycontinue self-carrier scheduling via one or more search spaces of thefirst cell. The base station 2204 may configure/indicate a second searchspace (e.g., SS2) of the first cell. The base station 2204 may send(e.g., step 2240), via the SS2, second DCI (e.g., DCI-2 2220).

The wireless device 2208 may receive (e.g., step 2258), via the SS2 ofthe first cell, the DCI-2 2220, for example, based on the cross-carrierscheduling being activated. The DCI-2 2220 may schedule resourceassignments for an SIB transmission (or any other downlink/uplinktransmission). The resource assignments may correspond to resourcesassociated with the first cell. The base station 2204 may send (e.g.,step 2241), via the first cell, a transmission scheduled by the DCI-22220. The wireless device 2208 may receive (e.g., step 2260) thetransmission (e.g., an SIB transmission 2222), for example, via thefirst cell and based on the DCI-2 2220. The DCI-2 2220 may compriseresource assignments for an RAR transmissions. The wireless device 2208may receive the RAR transmission, for example, based on the DCI 2220.

The base station 2204 may configure a third search space (SS3) of thesecond cell. The base station 2204 may send (e.g., step 2242), via theSS3, third DCI (e.g., DCI-3 2224). The DCI-3 2224 may schedule datatransmission via the first cell, for example, based on the cross-carrierscheduling being activated. The wireless device 2208 may receive (e.g.,step 2262) the DCI-3 2224 via the SS3 of the SCell. The DCI-3 2224 mayschedule a downlink transmission 2226 via the first cell. The basestation 2204 may send (e.g., step 2243), via the first cell, atransmission scheduled by the DCI-3 2224. The wireless device 2208 mayreceive (e.g., step 2264) a downlink transmission 2226, for example, viathe first cell and based on the DCI-3 2224.

FIG. 22D and FIG. 22E show an example method 2270 that may be performedby the base station 2204 and an example method 2286 that may beperformed by the wireless device 2208, respectively, for cross-carrierscheduling and self-carrier scheduling. Steps 2272-2284 of FIG. 22D maybe similar to steps 2236-2243, respectively, as described with referenceto FIG. 22B. Steps 2288-2298 of FIG. 22E may be similar to steps2254-2264, respectively, as described with reference to FIG. 22C.

The wireless device 2208 may enable or disable cross-carrier schedulingof first cell. The command 2218 may be an SCell activation MAC CE. Thecommand 2218 may be a scheduling DCI indicating an activation ofcross-carrier scheduling. The command 2218 may be an RRC message (e.g.,comprising an indicator/index of the second cell). The wireless device2208 may receive another command to disable or deactivate thecross-carrier scheduling for the first cell. The wireless device 2208may switch back to self-carrier scheduling, for example, based onreceiving the another command.

The first cell (e.g., a scheduled cell) and the second cell (e.g., ascheduling cell) may belong to a same cell group. The first cell and thesecond cell may belong to a same PUCCH group. The command 2218indicating/activating cross-carrier scheduling may be sent/transmittedvia RRC signaling, MAC CE signaling, and/or DCI signaling.

A base station may configure one or more parameters related tocross-carrier scheduling for a first cell. A wireless device mayactivate the cross-carrier scheduling for the first cell, for example,based on the one or more parameters. The wireless device may activatethe cross-carrier scheduling for the first cell, for example, basedon/in response to receiving a command. The command may indicate anactivation of a scheduling cell configured for the cross-carrierscheduling for the first cell. The wireless device may fallback toself-carrier scheduling for the first cell and/or may disable thecross-carrier scheduling for the first cell, for example, based on oneor more considerations (e.g., occurrence of one or more events). The oneor more events may comprise the wireless device switching to an initialDL and/or initial UL BWP of the first cell. The wireless device maydisable cross-carrier scheduling or may not apply cross-carrierscheduling, for example, if an active BWP is the initial DL BWP and/orthe initial UL BWP. The one or more events may comprise an expiration ofa BWP inactivity timer of the first cell at the wireless device. Thewireless device may switch to a default BWP of the first cell, forexample, based on an expiration of the BWP inactivity timer. Thewireless device may disable cross-carrier scheduling, for example, ifthe active BWP is the default BWP. The one or more events may comprisethe wireless device receiving a command indicating deactivation of thescheduling cell, wherein the cross-carrier scheduling is not supported.The one or more events may comprise the wireless device receiving acommand comprising a dormancy indication of the scheduling cell. Thewireless device may not monitor any search space of the scheduling cellthat is in a dormant state. The one or more events may comprise thewireless device triggering a PRACH transmission and switching back tothe initial DL BWP. The one or more events may comprise the wirelessdevice starting a random access procedure. The one or more events maycomprise the wireless device determining a beam failure of thescheduling cell and starting a beam recovery procedure for thescheduling cell. The one or more events may comprise the wireless devicereceiving a command to deactivate cross-carrier scheduling for the firstcell.

FIG. 23A shows an example of switching between cross-carrier schedulingand self-carrier scheduling. Cross-carrier scheduling may be deactivatedbased on an event as described above. The wireless device may switch tousing self-carrier scheduling based on deactivation of cross-carrierscheduling. FIG. 23B and FIG. 23C show example methods at a base station2304 and a wireless device 2308, respectively, for cross-carrier andself-carrier scheduling.

The base station 2304 may send (e.g., step 2332), to the wireless device2308, one or more configuration messages (e.g., RRC messages). The oneor more configuration messages may comprise parameters for cross-carrierscheduling (e.g., cross-carrier configuration 2312) of a first cell(e.g., PCell, primary cell). The one or more parameters may comprise ascheduling cell indicator/index of a second cell (e.g., SCell, secondarycell).

The wireless device 2308 may receive (e.g., step 2352) the one or moreconfiguration messages. The wireless device 2308 may activate (e.g.,step 2354) cross-carrier scheduling for the first cell, for example,based on receiving the one or more configuration messages. The basestation 2304 may send/transmit (e.g., step 2334) first DCI (DCI-1 2316)via a search space of second cell. The DCI-1 2316 may comprise resourceassignment(s) for data scheduled for the first cell. The wireless device2308 may receive (e.g., step 2356), via the search space of the secondcell, the DCI-1 2316. The base station 2304 may send (e.g., step 2335),via the first cell, data 2320 as scheduled by the DCI-1 2316. Thewireless device 2308 may receive (e.g., step 2358), via the first cell,data 2320 scheduled by the DCI-1 2316.

The wireless device 2308 may switch to self-carrier scheduling and/ordisable the cross-carrier scheduling for the first cell, for example,based on/in response to an event 2322 (e.g., an event as describedabove). For example, the base station 2304 may send (e.g., step 2336) acommand indicating deactivation of the second cell. The wireless device2308 may disable cross-carrier scheduling and/or enables self-carrierscheduling, for example, based on the event 2322. The base station 2304may send/transmit (e.g., step 2340) second DCI (DCI-2 2324) via a secondsearch space of the first cell. The DCI-2 2324 may schedule resourceassignment(s) for data scheduled for the first cell. The base station2304 may send (e.g., step 2342), via the first cell, data 2328 asscheduled by the DCI-2 2324. The wireless device 2308 may receive (e.g.,step 2362), via the first cell, data 2328 scheduled by the DCI-2 2324,for example, based on cross-carrier scheduling being deactivated andbased on receiving the DCI-2 2324 (e.g., step 2360).

FIG. 23D and FIG. 23E show an example method 2370 that may be performedby the base station 2304 and an example method 2382 that may beperformed by the wireless device 2308, respectively, for cross-carrierscheduling and self-carrier scheduling. Steps 2372-2380 of FIG. 23D maybe similar to steps 2334-2342, respectively, as described with referenceto FIG. 23B. Steps 2384-2392 of FIG. 23E may be similar to steps2354-2362, respectively, as described with reference to FIG. 23C.

Various examples described herein (e.g., with reference to FIGS. 22A-Cand FIGS. 23A-C) may be applied for scheduling downlink transmissions oruplink transmissions. With reference to FIG. 22A, for example, the DCIs(e.g., DCI-1 2214, DCI-2 2220, or DCI-3 2224) may schedule resources foreither a downlink transmission or an uplink transmission. With referenceto FIG. 23A, for example, the DCIs (e.g., DCI-1 2316 and DCI-2 2324) mayschedule resources for either a downlink transmission or an uplinktransmission.

A base station may configure a wireless device with self-carrierscheduling for a cell at least for an initial DL BWP. The cell may be aprimary cell of a cell group (e.g., PCell, SPCell) or a PUCCH SCell. Thebase station may configure cross-carrier scheduling for the cell for thewireless device, wherein an active DL BWP of the cell may be a first DLBWP. The first DL BWP may be the initial DL BWP. The first DL BWP may bea non-initial DL BWP. The first DL BWP may or may not be a default DLBWP. The first DL BWP may not be the initial DL BWP. The base stationmay send/transmit one or more configuration messages (e.g., RRCmessages). The one or more messages may comprise one or more parametersfor cross-carrier scheduling for the cell (e.g., cross-carrierconfiguration 2212 or 2312). The base station may configure across-carrier scheduling configuration (e.g., higher layer parameterCrossCarrierSchedulingConfig) as a part of one or more parametersconfigured for the cell (e.g., higher layer parameterServingCellConfig). The cross-carrier scheduling configuration maycomprise an indicator (e.g., cif-Presence) for a second cell (e.g., ascheduling cell for the cell). The indicator may indicate whether acarrier indicator field is present in DCI (e.g., from the second cell toschedule resources of the cell). The cross-carrier schedulingconfiguration may comprise one or more additional parameters (e.g.,schedulingCellId and cif-InSchedulingCell) for the cell. The parameterschedulingCellId may comprise an indicator/index (e.g.,servingcellindex) corresponding to the second cell. The parametercif-InSchedulingCell may indicate an indicator/index for the cell inDCI, via the second cell, scheduling resources in the cell.

The cross-carrier scheduling configuration may be configured for thecell. The cell may be the primary cell of the cell group or the PUCCHSCell. The wireless device may or may not activate the one or moreparameters of the cross-carrier scheduling configuration, for example,based on/in response to the receiving the cross-carrier schedulingconfiguration for the cell. The base station may indicate activation ofthe cross-carrier scheduling configuration for the cell via anothermessage. The another message may be an RRC message (e.g., indicatingconfiguration of a BWP enabled with cross-carrier scheduling, aconfiguration of a BWP with one or more search spaces enabled withcross-carrier scheduling), a MAC CE (e.g., an SCell activation MAC CE,comprising an enable/disable indication), and/or DCI (e.g., comprisingenable/disable indication). Cross-carrier scheduling configuration maybe activated, for example, after the cross-carrier schedulingconfiguration is configured. The wireless device may activate thecross-carrier scheduling configuration of the cell, for example, basedon/in response to the second cell being activated. The wireless devicemay activate the cross-carrier scheduling configuration of the cell, forexample, based on/in response to receiving an indication for activationof (or after activating) a DL BWP of the second cell that is differentfrom a default BWP of the second cell, a first active DL BWP of thesecond cell, or a dormant DL BWP of the second cell. The first active DLBWP of the second cell may be a DL BWP indicated in a serving cellconfiguration of the second cell. The wireless device may activate thefirst active DL BWP, for example, based on/in response to receiving anactivation command for the second cell. The dormant DL BWP of the secondcell may be a DL BWP that the wireless device switches to based onreceiving a dormancy indication for the second cell.

Cross-carrier scheduling configuration may be configured for a DL BWP ofthe cell (e.g., instead of being configured for the cell). A basestation may configure a first cross-carrier scheduling configuration fora first DL BWP of the cell. The base station may not configure thecross-carrier scheduling configuration for a second DL BWP of the cell.The base station may configure a second cross-carrier schedulingconfiguration for a third DL BWP of the cell. The first cross-carrierscheduling configuration may indicate a first SCell as a schedulingcell. The second cross-carrier scheduling configuration may indicate asecond SCell as a scheduling cell. The wireless device may receive oneor more first DCIs, from the first SCell, for scheduling downlink/uplinkdata for the cell, for example, if the first DL BWP is an active DL BWP.The wireless device may receive one or more second DCIs, from the secondSCell, for scheduling downlink/uplink data for the cell, for example, ifthe active DL BWP is the third active DL part. The wireless device mayswitch from cross-carrier scheduling to self-carrier scheduling, forexample, if the wireless device switches from the first DL BWP or thethird DL BWP to the second DL BWP. The wireless device may assume thatself-carrier scheduling is used for the cell, for example, if an activeDL BWP is not configured with the cross-carrier schedulingconfiguration. The wireless device may assume that self-carrierscheduling is used for the cell, for example, if the second DL BWP isthe active DL BWP.

A base station may configure a first cross-carrier schedulingconfiguration for a first DL BWP of a second cell. The second cell maybe a scheduling cell for a first cell. The base station may notconfigure cross-carrier scheduling configuration for a second DL BWP ofthe second cell. The base station may configure a second cross-carrierscheduling configuration for a third DL BWP of a second cell. Thewireless device may assume self-carrier scheduling or cross-carrierscheduling by the second cell, for the first cell, for example, based onan active DL BWP of the second cell. The wireless device may assumeself-carrier scheduling for the first cell, for example, if the activeDL BWP of the second cell is the second DL BWP (e.g., wherecross-carrier scheduling configuration is not configured or disabled).The wireless device may assume cross-carrier scheduling, for the firstcell, based on the first cross-carrier scheduling configuration, forexample, if the active DL BWP of the second cell is the first DL BWP(e.g., where the first cross-carrier scheduling configuration isconfigured). The wireless device may assume cross-carrier scheduling,for the first cell, based on the third cross-carrier schedulingconfiguration, for example, if the active DL BWP of the second cell isthe third DL BWP (e.g., where the third cross-carrier schedulingconfiguration is configured). Cross-carrier scheduling configuration maybe applied per BWP of the first cell and/or BWP of the second cell.

A base station may configure a plurality of cells of a cell group for awireless device. The base station may configure a PUCCH cell among theplurality of cells of the cell group. The wireless device may support afirst PUCCH group comprising a primary cell of the cell group and one ormore first secondary cells (e.g., SCells). HARQ-ACK feedbacks of the oneor more first SCells may be sent/transmitted via the primary cell. Thewireless device may support a second PUCCH group comprising the PUCCHcell and one or more second SCells. HARQ-ACK feedbacks f the one or moresecond SCells may be sent/transmitted via the PUCCH cell. The basestation may configure a first SCell as a scheduling cell for the primarycell of the cell group. The base station may select the first SCell,from the one or more first SCells, such that the scheduling cell of theprimary cell and the primary cell of the cell group belong to a samePUCCH group (e.g., the first PUCCH group). The base station mayconfigure a second SCell as a scheduling cell for the PUCCH cell of thecell group. The base station may select the second SCell, from the oneor more second SCells, such that the scheduling cell of the PUCCH celland the PUCCH cell of the cell group belong to a same PUCCH group (e.g.,the second PUCCH group).

The base station may configure a scheduling cell of a cell (e.g.,primary cell or PUCCH cell of the cell group). The scheduling cell maybelong to a PUCCH group different from a PUCCH group of the cell. Thescheduling cell may be configured with PUCCH-cell as the primary cellwhereas the cell may be the PUCCH cell and the scheduling cell may befor the PUCCH cell, or the scheduling cell may be configured withPUCCH-cell as the PUCCH cell whereas the cell may be the primary celland the scheduling cell may be for the primary cell. The wireless devicemay send/transmit first HARQ-ACK feedbacks corresponding to thescheduling cell via the PUCCH-cell configuration of the scheduling cell.The PUCCH-cell of the scheduling cell may be same or different from thecell. The wireless device may send/transmit second HARQ-ACK feedbackscorresponding to the cell via the cell.

A base station may configure cross-carrier scheduling for a first cell.The base station may configure the cross-carrier scheduling for at leasta DL BWP of the first cell. A wireless device may be activated with thefirst cell and the wireless device may or may not be activated with asecond cell, for example, at a time of the configuration. The secondcell may be a scheduling cell for the first cell. The wireless devicemay be configured with the second cell at a time of the configuration.The base station may configure the second cell as the scheduling cellfor the first cell via one or more RRC messages, MAC CEs, and/or DCIs.The wireless device may determine whether to apply self-carrierscheduling or cross-carrier scheduling for a first DL BWP of the firstcell (e.g., wherein the first DL BWP is an active DL BWP of the firstcell), for example, based on one or more parameters of the cross-carrierscheduling comprising the scheduling cell for the first cell and astatus of the scheduling cell.

The wireless device may apply cross-carrier scheduling, for example, ifthe scheduling cell becomes activated (e.g., via MAC CE and/or DCIsignaling). The MAC CE may be an SCell activation/deactivation command.The wireless device may activate cross-carrier scheduling of the firstcell, for example, if the scheduling cell becomes activated via thesignaling. The wireless device may continue self-carrier scheduling, forexample, until cross-carrier scheduling of the first cell is activated(e.g., at or after a time t). The time t may be determined based on adelay associated with the scheduling cell activation latency. Theactivation latency may be 3 ms (e.g., or any other time period), forexample, after receiving the MAC CE activation command. The wirelessdevice may start the cross-carrier scheduling of the first cell, forexample, 3 ms (or any other time period) after receiving the MAC CE. Thewireless device may start cross-carrier scheduling, for example, afterthe scheduling cell is activated and after a delay T following theactivation. The wireless device may receive an activation command forthe scheduling cell at a first time. The wireless device may activatethe scheduling cell at the first time+SCell activation latency (e.g., 3ms, 3 slots, 8 slot, and/or any other period of time, any other quantityof slots). The wireless device may start a timer to count the delay T,for example, after the scheduling cell is activated. The wireless devicemay start the cross-carrier scheduling for the first cell at the firsttime+SCell activation latency+T. The wireless device may continueself-carrier scheduling for the first cell, for example, at least untilthe first time+SCell activation latency.

The wireless device may switch from a second DL BWP to the first DL BWP,for example, based on/in response to the scheduling cell beingactivated. The delay T may be a BWP switching latency. The wirelessdevice may activate the scheduling cell. The wireless device may performBWP switching to a BWP of the first cell, for example, based on/inresponse to the scheduling cell of the first cell being activated andbased on cross-carrier scheduling being configured for the BWP. Thewireless device may select a lowest BWP indicator/index, among theindicators/indices of the plurality of the BWPs, to switch to (e.g.,unless an active BWP is configured also with the cross-carrierscheduling), for example, if the wireless device is configured with aplurality of BWPs where cross-carrier scheduling is configured orenabled. The wireless device may stay in the current BWP, for example,if the active BWP is configured with cross-carrier scheduling. The delayT may be zero, for example, if the wireless device stays in the currentBWP. The wireless device may apply cross-carrier scheduling at the timeat which the scheduling cell is activated.

Self-carrier scheduling or cross-carrier scheduling may beconfigured/associated with a DL BWP of the first cell. Scheduling of aUL BWP of the first cell (e.g., via UL grants) may follow the active DLBWP of the first cell.

A base station may configure cross-carrier scheduling configuration fora first cell. The cross-carrier scheduling configuration may comprise aparameter of a scheduling cell. The base station may configure aparameter (e.g., CrossCarrierSchedulingEnabled orCrossCarrierSchedulingDisabled) for a DL BWP of the first cell. Thewireless device may assume that a first DL BWP is configured with aself-carrier scheduling (e.g., CrossCarrierSchedulingDisabled), forexample, if the parameter is not provided for the first DL BWP. Thewireless device may consider that cross-carrier scheduling (e.g.,CrossCarrierSchedulingEnabled) as a default value, for example, if aparameter per DL BWP is not available and cross-carrier schedulingconfiguration is available for the first cell. The default value may bedifferent for a DL BWP. The wireless device may assume self-carrierscheduling for an initial DL BWP of the first cell. The wireless devicemay assume cross-carrier scheduling for a non-initial DL BWP of thefirst cell, for example, if cross-carrier scheduling configuration isconfigured for the first cell.

The wireless device may switch back to self-carrier scheduling for thefirst cell, for example, if the scheduling cell is in an inactive state,the scheduling cell is in a dormant state, the scheduling cell is in adeactivated state, the scheduling cell is in a DRX OFF state, in case ofbeam failure, or in case of radio link failure of the scheduling cell.The scheduling cell may be deactivated by a MAC CE deactivation command.The wireless device may switch back to self-carrier scheduling. Thewireless device may switch back to self-carrier scheduling, for example,based on/in response to the receiving of the deactivation command forthe scheduling cell. The wireless device may apply the latency T forswitching between cross-carrier scheduling and the self-carrierscheduling for the first cell. The latency T may follow the reception ofthe deactivation command. The wireless device may switch back toself-carrier scheduling, for example, if the wireless device sends abeam failure request for the scheduling cell, or if the wireless devicedetermines a beam failure for the scheduling cell. The beam failurerequest may be sent/transmitted via the first cell. A response for thebeam failure request may be received via the first cell based onself-carrier scheduling.

The wireless device may switch back to self-carrier scheduling, forexample, if the scheduling cell enters a dormant state based on acommand and/or a timer. The wireless device may switch the schedulingcell into the dormant state and/or may switch to self-carrier schedulingfor the first cell, for example, based on the base station requestingthe scheduling cell to enter the dormant state. The wireless device mayswitch back to self-carrier scheduling for the first cell, for example,if the wireless device is in a DRX OFF state or a sleep state for thescheduling cell and if the wireless device is not in a DRX OFF state orsleep state for the first cell.

A first base station may configure, for a wireless device, one or morefirst cells of a first cell group. A second base station may configure,for the wireless device, one or more second cells of a second cellgroup. The first base station and/or the second base station mayindicate a cell group indicator/index in MAC CEs and/or DCIs. The MACCEs and/or DCIs may be transmitted by either base station for the otherbase station.

FIG. 24A shows an example method for switching between cross-carrierscheduling and self-carrier scheduling. The example method 2400 may beperformed by a wireless device. The wireless device may enablecross-carrier scheduling based on configuration if one or moreconditions are being met, for example, after initial access. Thewireless device may enable cross-carrier scheduling, for example, if anactive BWP is not an initial BWP. The wireless device may enablecross-carrier scheduling, for example, if a scheduling cell for aprimary cell is active. Otherwise, the wireless device continuesself-carrier scheduling for primary cell.

At step 2404, the wireless device may receive one or more RRCparameters. The one or more RRC parameters may comprise a schedulingcell indicator/index for the primary cell. At step 2408, the wirelessdevice may send, via the primary cell, a PRACH transmission. At step2412, the wireless device may receive an RAR via the primary cell.

At step 2416, the warless device may determine whether an active DL BWPfor the primary cell is an initial DL BWP. At step 2424, the wirelessdevice may disable cross-carrier scheduling for the primary cell if theactive DL BWP is an initial DL BWP. At step 2420, the wireless devicemay determine if a scheduling cell if active, for example, if the activeDL BWP is not an initial DL BWP. At step 2428, the wireless device mayenable cross-carrier scheduling for the primary cell if the wirelessdevice determines that the scheduling cell is active. The wirelessdevice may disable cross-carrier scheduling if the wireless devicedetermines that the scheduling cell is not active.

FIG. 24B shows an example method for switching between cross-carrierscheduling and self-carrier scheduling. The example method 2450 may beperformed by a wireless device. Steps 2458-2478 of FIG. 24B may besimilar to steps 2408-2428, respectively, as described with reference toFIG. 24A.

FIG. 25A shows an example method for monitoring search spaces. Theexample method 2500 may be performed by a wireless device. The wirelessdevice may monitor a first search space of the primary cell regardlessof whether cross-carrier scheduling is enabled or disabled. The wirelessdevice may monitor a third search space of a scheduling cell for aprimary cell, for example, if cross-carrier scheduling is enabled forthe primary cell. The wireless device may stop monitoring a secondsearch space of the primary cell, for example, based on activating thecross-carrier scheduling.

At steps 2504 and 2508, the wireless device may receive one or more RRCparameters. The one or more RRC parameters may comprise a schedulingcell indicator/index for the primary cell. The one or more RRCparameters may indicate the first search space and the second searchspace of the primary cell. The one or more RRC parameters may indicatethe third search space of the scheduling cell.

At step 2512, the warless device may determine whether an active DL BWPfor the primary cell is an initial DL BWP. At step 2520, the wirelessdevice may monitor the first search space and the second search space ofthe primary cell, for example, if the active DL BWP for the primary cellis an initial DL BWP. At step 2516, the wireless device may determine ifa scheduling cell if active, for example, if the active DL BWP is not aninitial DL BWP. At step 2428, the wireless device may monitor the firstsearch space of the primary cell and the third search space of thescheduling cell, for example, if the wireless device determines that thescheduling cell is active. The wireless device may monitor the firstsearch space and the second search space of the primary cell if thewireless device determines that the scheduling cell is not active.

FIG. 25B shows an example method for monitoring search spaces. Theexample method 2550 may be performed by a wireless device. Steps2558-2574 of FIG. 25B may be similar to steps 2508-2524, respectively,as described with reference to FIG. 25A.

A wireless device may receive one or more messages. The one or moremessages may comprise configuration parameters for a first cell. Theconfiguration parameters may indicate a first search space formonitoring for DCIs of a downlink control channel of the first cell. Theconfiguration parameters may indicate a second search space formonitoring for DCIs of the downlink control channel of the first cell, athird search space for monitoring for DCIs of the downlink controlchannel of a second cell, and one or more parameters for a cross-carrierscheduling. The one or more parameters may indicate that the second cellis a scheduling cell of the first cell. The wireless device may monitorthe first search space of the first cell for first DCI. The wirelessdevice may monitor the second search space of the first cell for secondDCI comprising resource assignments for the first cell. The wirelessdevice may receive a command indicating switching from self-carrierscheduling to cross-carrier scheduling for the first cell. The wirelessdevice, based on the receiving, may continue monitoring the first searchspace of the first cell for the first DCI, stop monitoring the secondsearch space of the first cell, and start monitoring the third searchspace of the second cell for a third DCI comprising resource assignmentsfor the first cell.

A wireless device may receive one or more messages. The one or moremessages may comprise configuration parameters for a first cell. Theconfiguration parameters may indicate a first search space formonitoring for DCIs of a downlink control channel of the first cell. Theconfiguration parameters may indicate a second search space formonitoring for DCIs of the downlink control channel of the first cell, athird search space for monitoring for DCIs of the downlink controlchannel of a second cell, and one or more parameters for a cross-carrierscheduling. The one or more parameters may indicate that the second cellis a scheduling cell of the first cell. The wireless device may monitorthe first search space of the first cell for first DCI. The wirelessdevice may monitor the third search space of the second cell for secondDCI comprising resource assignments for the first cell. The wirelessdevice may receive a command indicating switching from cross-carrierscheduling to self-carrier scheduling for the first cell. The wirelessdevice, based on the receiving, may continue monitoring the first searchspace of the first cell for the first DCI, stop monitoring for the thirdsearch space of the second cell, and start monitoring the second searchspace of the first cell for a third DCI comprising resource assignmentsfor the first cell.

A wireless device may receive one or more messages. The one or moremessages may comprise configuration parameters for a first cell. Theconfiguration parameters may indicate a scheduling cell indicator/index,a first DL BWP, and a second DL BWP. The wireless device may activatethe first DL BWP of the first cell as an active DL BW of the first cell.The wireless device may determine to use self-carrier scheduling basedon the activating the first DL BWP. The wireless device may monitor oneor more first search spaces of the first cell for receiving first DCIs(e.g., comprising resource assignments for the first cell), for example,based on the determining. The wireless device may receive a command toswitch to the second DL BWP as the active DL BWP of the first cell. Thewireless device may apply the one or more parameters for cross-carrierscheduling, for example, based on the receiving the command. Thewireless device may monitor one or more second search spaces of thescheduling cell for receiving second DCIs (e.g., comprising resourceassignments for the first cell).

A wireless device may receive one or more messages. The one or moremessages may comprise configuration parameters for a first cell. Theconfiguration parameters may indicate a scheduling cell indicator/index,an initial DL BWP, and a second DL BWP. The wireless device may activatethe initial DL BWP of the first cell as an active DL BW of the firstcell. The wireless device may determine to use self-carrier scheduling,for example, based on the activating the initial DL BWP. The wirelessdevice may monitor one or more first search spaces of the first cell forreceiving first DCIs (e.g., comprising resource assignments for thefirst cell), for example, based on the determining. The wireless devicemay receive a command to switch to the second DL BWP as the active DLBWP of the first cell. The wireless device may apply the one or moreparameters for cross-carrier scheduling, for example, based on receivingthe command. The wireless device may monitor one or more second searchspaces of the scheduling cell for receiving second DCIs (e.g.,comprising resource assignments for the first cell).

FIG. 26A shows an example of switching between self-carrier schedulingand cross-carrier scheduling. The switching between self-carrierscheduling and cross carrier scheduling may be based on BWP switching.The switching between self-carrier scheduling and cross carrierscheduling may comprise BWP switching based on receiving a commandindicating switching between self-carrier scheduling and cross-carrierscheduling. FIG. 26B and FIG. 26C show example methods that may beperformed by a base station 2604 and a wireless device 2608,respectively, for cross-carrier scheduling and self-carrier scheduling.

The base station 2604 may send/transmit (e.g. at step 2632) one or moreRRC messages 2610. The wireless device 2608 may receive (e.g., at step2652) the one or more RRC messages 2610. The one or more RRC messages2610 may comprise one or more parameters related to a cross-carrierscheduling. The wireless device 2608 may receive the one or more RRCmessage 2610 comprising the one or more parameters. The wireless device2608 may be configured with a plurality of cells. The plurality of cellmay comprise a first cell (e.g., cell 0, primary cell) and a second cell(e.g., cell 1, secondary cell). The base station 2604 may configure(e.g., via the one or more RRC messages 2610) one or more parameters forcross-carrier scheduling for the first cell. The second cell may beconfigured as a scheduling cell for the first cell. The base station2604 may configure a first BWP (e.g., BWP 1 2616, initial BWP) and asecond BWP (e.g., BWP 2 2620, non-initial BWP, non-default BWP) for thefirst cell. The first BWP may be associated/configured with self-carrierscheduling. The second BWP may associated/configured with thecross-carrier scheduling. The one or more parameters may comprise anindicator/index of the second cell.

The wireless device 2608 may activate the first BWP, for example, via aninitial access procedure. The wireless device 2608 may apply theself-carrier scheduling, for example, if the first BWP is an active BWPof the first cell. The base station may send/transmit (e.g., step 2636)first DCI (DCI-1 2612) via a first search space (SS1) of the first cell,for example, based on self-carrier scheduling. The first search spacemay be associated with the first BWP. The first DCI may schedule a firstdata transmission (e.g., data 2614) for the first cell. The wirelessdevice 2608 may receive (e.g., step 2654), via the first search space ofthe first cell, the first DCI. The base station 2604 may send (e.g.,step 2637), via the first BWP of the first cell, the first datatransmission as scheduled by the first DCI. The wireless device 2608 mayreceive (e.g., step 2656), via the first BWP of the first cell and basedon the first DCI, the first data transmission.

The base station 2604 may send (e.g., step 2638) a command 2618activating cross-carrier scheduling for the first cell. The command 2618may be DCI indicating BWP switching from the first BWP to the secondBWP. The command 2618 may be DCI indicating a transition tocross-carrier scheduling. The command 2618 may be a MAC CE indicating anactivation of the second cell.

The wireless device 2608 may transition to the second BWP of the firstcell, for example, based on receiving the command. The wireless device2608 may use cross-carrier scheduling, for example, if the second BWP isthe active BWP (e.g., based on transitioning to the second BWP). Thebase station 2604 may send/transmit (e.g., step 2640) second DCI (DCI-22622) via a second search space (e.g., SS2) of the second cell, forexample, based on cross-carrier scheduling. The second search space maycorrespond to a third DL BWP (e.g., of the second cell) and may beassociated with a search space of the second DL BWP of the first cell.The second DCI may schedule a second data transmission (e.g., data 2624)for the first cell. The wireless device 2608 may receive (e.g., step2662), via the second search space of the second cell, the second DCI.The base station 2604 may send (e.g., step 2642), via the second BWP ofthe first cell, the second data transmission as scheduled by the secondDCI. The wireless device 2608 may receive (e.g., step 2664), via thesecond BWP of the first cell and based on the second DCI, the seconddata transmission.

FIG. 26D and FIG. 26E show an example method 2670 that may be performedby the base station 2604 and an example method 2682 that may beperformed by the wireless device 2608, respectively, for switchingbetween self-carrier scheduling and cross-carrier scheduling. Steps2672-2680 of FIG. 26D may be similar to steps 2636-2642, respectively,as described with reference to FIG. 26B. Steps 2684-2690 of FIG. 26E maybe similar to steps 2654-2664, respectively, as described with referenceto FIG. 26C.

The example communication described with reference to FIGS. 26A-E may beapplied for scheduling downlink transmissions or uplink transmissions.With reference to FIGS. 26A, for example, the DCIs (e.g., DCI-1 2612and/or DCI-2 2622) may schedule resources for either a downlinktransmission or an uplink transmission.

A wireless device may use cross-carrier scheduling for a first cell. Thewireless device may use one or more following approaches to monitoringreception of one or more DCIs comprising resource assignments for thefirst cell. The wireless device may monitor, for the one or more DCIs,one or more search spaces of a scheduling cell (e.g., a second cell) andthe wireless device may not monitor any search space of the first cell.The wireless device may monitor, for one or more second DCIs (e.g.,group-common DCI), one or more first search spaces of the first cell.The wireless device may monitor, for the one or more DCIs, one or morefirst search spaces of the second cell and one or more second searchspaces of the first cell. The wireless device may monitor, for the oneor more DCIs, the one or more search spaces of the second cell. Thewireless device may monitor, for one or more third DCIs (e.g., DCIsbased on a fallback DCI format, such as DCI format 0_0/1_0), one or morethird spaces of the first cell. The wireless device may monitor one ormore wireless device-specific search spaces of the second cell forreceiving one or more scheduling DCIs for the first cell. The wirelessdevice may monitor one or more cell-specific search spaces of the firstcell for receiving one or more second scheduling DCIs for the firstcell. The one or more second scheduling DCIs may schedule broadcastdata. The one or more second scheduling DCIs may be sent/transmittedbased on a fallback DCI format (e.g., DCI format 0_0/1_0).

FIG. 27 shows an example configuration of a BWP. A wireless device mayreceive (e.g., from a base station) one or more BWP DL configurations(e.g., BWP-Downlink). A BWP DL configuration may comprise one or more ofa BWP indicator (e.g., bwp-Id), a common BWP DL configuration (e.g.,BWP-DownlinkCommon), and/or a dedicated BWP downlink configuration(e.g., BWP-DownlinkDedicated). The common BWP DL configuration maycomprise one or more of a BWP configuration, a common PDCCHconfiguration (e.g., PDCCH-ConfigCommon), and/or a common PDSCHconfiguration (e.g., PDSCH-ConfigCommon). The common PDCCH configurationmay comprise a set of parameters for receiving DCI comprising a resourceassignment for common data or common DCI. The common PDSCH configurationmay comprise a set of parameters for receiving broadcast data or unicastdata. The dedicated BWP DL configuration may comprise a set ofparameters for a PDCCH configuration (e.g., PDCCH-Config), a PDSCHconfiguration (e.g., PDSCH-Config), an SPS configuration (e.g.,SPS-Config), or RLM-RS configurations. The PDCCH configuration maycomprise a set of parameters for CORESETs, search space sets, andrelated scrambling information and beam information to receive DCI. ThePDSCH configuration may comprise/indicate a list of time-domain resourceallocation entries, rate matching patterns, and/or scramblinginformation for downlink data. The parameters of a BWP configuration maycomprise/indicate location and bandwidth information (e.g., frequencylocation and bandwidth of a BWP), subcarrier spacing, and/or cyclicprefix (e.g., numerology of a BWP).

The base station may configure a first PDCCH configuration (e.g., firstPDCCH-Config) and a second PDCCH configuration (e.g., secondPDCCH-Config) associated with a first DL BWP of a first cell. The firstDL BWP of the first cell may be indicated by the BWP indicator. Thefirst PDCCH configuration may comprise/indicate a first set of searchspaces for the first DL BWP. The first set of search spaces may beconfigured with self-carrier scheduling. The second PDCCH configuration(e.g., second PDCCH-Config) may comprise/indicate a second set of searchspaces for the first DL BWP. The second set of search spaces may beconfigured with cross-carrier scheduling. The base station may configurecross-carrier scheduling configuration (e.g.,CrossCarrierSchedulingConfig) for the first cell. The cross-carrierscheduling configuration may comprise a scheduling cell indicator/index.The base station may enable or disable the cross-carrier scheduling forthe first cell and/or for the first DL BWP of the first cell, forexample, based on one or more MAC CEs and/or one or more DCIs (e.g., thecommand 2618 as described with reference to FIG. 26A). The wirelessdevice may apply the second PDCCH configuration, for example, ifcross-carrier scheduling is enabled. The first DL BWP may an active DLBWP of the first cell. The wireless device may apply the first PDCCHconfiguration, for example, if self-carrier scheduling is enabled. Thefirst DL BWP may be the active DL BWP of the first cell.

The base station may configure CORESETs for DL BWPs to enable a wirelessdevice to differentiate between DL BWPs configured with self-carrierscheduling and cross-carrier scheduling. A base station may configure afirst DL BWP with self-carrier scheduling for a first cell. The basestation may configure a second DL BWP with cross-carrier scheduling forthe first cell. The base station may or may not configure a set ofCORESETs for the first DL BWP to differentiate between self-carrierscheduling and cross-carrier scheduling for the first DL BWP. A wirelessdevice may consider that the first DL BWP is configured withself-carrier scheduling for example, if the set of CORESETs areconfigured for the first DL BWP. The wireless device may consider thatthe first DL BWP, configured with at least one CORESET, is configuredwith self-carrier scheduling, for example, if the at least one CORESETis associated with one or more wireless device-specific search spaces.The wireless device may consider that the second DL BWP is configuredwith cross-carrier scheduling, for example, if no CORESET configurationis available for the second DL BWP or no CORESET associated with awireless device-specific search space is configured for the second DLBWP. The second DL BWP may be configured with a first CORESET. The firstCORESET may be associated with one or more common search spaces. Thewireless device may consider that the second DL BWP is configured withcross-carrier scheduling, for example, if the first CORESET isconfigured with cross-carrier scheduling. The wireless device maydetermine whether a BWP is configured with self-carrier scheduling orcross-carrier scheduling based on CORESET configuration associated witha set of search spaces of wireless device-specific search spaces. TheBWP may be configured with one or more CORESETs associated with commonsearch spaces, for example, if cross-carrier scheduling is enabled.

A base station may configure a first set of BWPs (e.g., a first BWP set)for a first cell. The first set of BWPs comprise one or more first DLBWPs of the first cell. The base station may configure a second set ofBWPs for the first cell. The second set of BWPs comprise one or moresecond DL BWPs of the first cell. The base station mayconfigure/associate self-carrier scheduling for the one or more first DLBWPs of the first set of BWPs. The base station may configure/associatedcross-carrier scheduling for the one or more second DL BWPs of thesecond set of BWPs. The base station may switch from a first BWP of theone or more first BWPs to a second BWP of the one or more second BWPs toenable cross-carrier scheduling for the first cell. The base station mayswitch from the second BWP to the first BWP to disable cross-carrierscheduling.

FIG. 28A shows an example configuration of a plurality of BWP sets for acell. The example configuration of the plurality of sets may enabledynamic enabling/disabling of cross-carrier scheduling for the cell asfurther described herein. A base station may configure multiple sets ofBWPs. Each set of BWP may be configured with either self-carrierscheduling or cross-carrier scheduling. One or more BWPs in the multiplesets may share BWP indicators/indices. BWP switching procedures may beused to switch between BWPs in a BWP set. An indicator of a BWP set maybe used to enable/disable cross-carrier scheduling. FIG. 28B and FIG.28C show example methods that may be performed by a base station and awireless device, respectively, for cross-carrier scheduling andself-carrier scheduling.

A base station may send (e.g., step 2832), to the wireless device, oneor more configuration messages indicating a first BWP set 2804 and/or asecond BWP set 2808 for the cell. The base station may configure, viathe one or more configuration messages, the first BWP set 2804 and/orthe second BWP set 2808, each comprising respective one or more BWPs.The first BWP set 2804 may comprise a BWP #0 (e.g., a BWP with BWPindicator/index 0, or an initial BWP), a BWP #N (e.g., a BWP with BWPindicator/index N, or a default BWP), and a BWP #P (e.g., a BWP with BWPindicator/index P, or a non-initial/non-default BWP). The first BWP set2804 may comprise any other quantity of BWPs. A wireless device mayconsider that an initial DL BWP and a default DL BWP may correspond tothe first BWP set 2804, for example, based on an explicit configurationfrom the base station (e.g., based on receiving configurationparameters). The wireless device may consider that an initial DL BWP anda default DL BWP may correspond to the first BWP set 2804, for example,without an explicit configuration from the base station. The basestation may use a BWP set indicator/ID (e.g., 0 or 1) to indicate a BWPset (e.g., the first BWP set 2804 or the second BWP set 2808) for anon-initial DL BWP and/or a non-default DL BWP. The wireless device mayexpect to be configured with the second BWP set 2804, for example, ifthe wireless device is configured with cross-carrier scheduling for thecell. The wireless device may receive (e.g., step 2852) the one or moreconfiguration messages.

One or more BWP indices may be shared between the first BWP set 2804 andthe second BWP set 2808. Sharing BWP indices between the first BWP set2804 and the second BWP set 2808 may enable reduced overhead forindicating BWP switching even if a quantity of BWPs is increased. Forexample, the second BWP set may also comprise a BWP with BWPindicator/index P). The base station may configure/associateself-carrier scheduling for one or more first DL BWPs of the first BWPset 2804. The base station may configure/associate cross-carrierscheduling for one or more second DL BWPs of the second BWP set 2808.

The wireless device may activate a first BWP of the first BWP set 2804(e.g., BWP #P of the first BWP set 2804) as an active BWP. The wirelessdevice may operate on the first BWP based on self-carrier scheduling forthe cell. The wireless device may monitor one or more search spacesconfigured for the first BWP (e.g., SS #s, . . . , SS #q). The basestation may send (e.g., step 2836), via a search space of the one ormore search spaces configured for the first BWP, first DCI schedulingtransmission (e.g., downlink transmission) via the cell. The wirelessdevice may receive (e.g., step 2854), the first DCI. The base station2804 may send (e.g., step 2837), via the first BWP of the cell, downlinkdata as scheduled by the first DCI. The wireless device may receive(e.g., step 2856), via the first BWP of the cell and based on the firstDCI, the downlink data.

The base station may send/transmit (e.g., step 2838) acommand/indication to enable cross-carrier scheduling for the cell. Thecommand may indicate a BWP set indicator of the second BWP set 2808. Thewireless device may determine (e.g., step 2862) a second BWP from thesecond BWP set 2808 based on the BWP indicator/index of the active BWPof the cell (e.g., the BWP indicator/index of the first BWP), forexample, based on/in response to receiving the command/indication. Thewireless device may determine the second BWP that shares a same BWPindicator/index as the first BWP. The wireless device may switch to thesecond BWP, for example, based on/in response to the determining. Thewireless device may further determine (e.g., step 2864) one or moresecond search spaces of a scheduling cell based on one or more firstsearch spaces of the second BWP. The second BWP may comprise SS #i, . .. , SS #j (e.g., corresponding to search space indicator/index i, . . ., a search space indicator/index j). The wireless device may determinethe one or more second search spaces, wherein a second search spaceindicator/index of a second search space of the one or more secondsearch spaces is same as a first search space indicator/index of a firstsearch space of the one or more first search spaces. The wireless devicemay determine the one or more second search spaces of the schedulingcell based on one or more search space indicators/indices of the one ormore first search spaces of an active DL BWP, for example, ifcross-carrier scheduling is enabled.

The base station may send (e.g., step 2840), via a search space of thescheduling cell, second DCI scheduling transmission (e.g., downlinktransmission) via the cell. The wireless device may receive (e.g., step2866), via a search space of the scheduling cell, the second DCI. Thebase station 2804 may send (e.g., step 2842), via the second BWP of thecell, downlink data as scheduled by the second DCI. The wireless devicemay receive (e.g., step 2868), via the second BWP of the cell and basedon the second DCI, the downlink data.

FIG. 28D and FIG. 28E show an example method 2870 that may be performedby a base station and an example method 2882 that may be performed by awireless device, respectively. Steps 2872-2880 of FIG. 28D may besimilar to steps 2836-2842, respectively, as described with reference toFIG. 28B. Steps 2884-2894 of FIG. 28E may be similar to steps 2854-2868,respectively, as described with reference to FIG. 28C.

The base station may send BWP switching DCI to the wireless device. TheBWP switching DCI may comprise a BWP indicator/index for a new active DLBWP. The wireless device may switch to the new active DL BWP. The activeDL BWP and the new active DL BWP may correspond to a same BWP set. TheBWP switching DCI may not switch between cross-carrier scheduling andself-carrier scheduling. The BWP switching DCI may switch between BWPscorresponding to a same BWP set. A DCI bit field size of the BWPswitching DCI may be determined based on a quantity of BWPs in the firstBWP set 2804 or the second BWP set 2808. The DCI bit field size may beequal to 2 bits, for example, if the first BWP set 2804 comprises 3BWPs. The DCI bit field size may be equal to any other quantity of bitsand may be determined based on a quantity of BWPs in the first BWP set2804 or the second BWP set 2804. K may be equal to a maximum quantity ofBWPs in a BWP set. The wireless device may not expect to be configuredwith more than K BWPs for each BWP set, wherein the K is a quantity ofBWPs supported with and without cross-carrier scheduling (e.g., K=4, orany other quantity).

The wireless device may experience an expiration of a BWP inactivitytimer of the cell. The wireless device may transition to the default BWPas the active DL BWP, for example, based on the expiration of the BWPinactivity timer. The wireless device may transition to the default BWPof the first BWP set 2804, for example, if the wireless device isactivated with the second BWP of second BWP set 2808 and if the defaultBWP is associated with self-carrier scheduling. A first default BWP anda second default BWP may be configured respectively in each BWP set(e.g., the first BWP set 2804 and the second BWP set 2808). The wirelessdevice may switch to the first default BWP, for example, if the currentactive BWP corresponds to the first BWP set 2804. The wireless devicemay switch to the second default BWP, for example, if the current activeBWP belongs to the second BWP set 2808. The current active BWP may bethe active BWP at a time of the expiration of the BWP inactivity timer.The wireless device may switch to the initial DL BWP regardless ofwhether the current active BWP belongs to the first BWP set 2804 or thesecond BWP set 2808, for example, if the wireless device is notconfigured with a default BWP.

A base station may configure a plurality of DL BWPs for a cell. The basestation may configure a first BWP with a first BWP indicator/index witha value that is less than K (e.g., the first BWP index <K). The basestation may configure a second BWP with a second BWP indicator/indexwith a value that is equal to or larger than K (e.g., the second BWPindex >=K). K may be equal to a quantity of BWPs supported by BWPswitching. The wireless device may determine whether the first BWPcorresponds to a BWP set configured for self-carrier scheduling (e.g., afirst BWP set) or a BWP set configured for cross-carrier scheduling(e.g., a second BWP set) based on the first BWP indicator/index. Thewireless device may determine that a BWP corresponds to the BWP setconfigured for self-carrier scheduling (e.g., the first BWP set), forexample, if a value of a BWP indicator/index of the BWP is less than K.Otherwise, the wireless device may determine that the BWP corresponds tothe BWP set configured for cross-carrier scheduling (e.g., the secondBWP set). The wireless device may determine that the first BWPcorresponds to the first BWP set and the second BWP corresponds to thesecond BWP set based on corresponding values of the BWP indicators. Thebase station may configure a BWP set based on a BWP indicator/index of aBWP. The wireless device may determine the second BWP set, for example,the base station configures one or more parameters for cross-carrierscheduling for the cell.

FIG. 29 shows an example configuration of a plurality of BWP sets for acell. BWPs may be grouped based on BWP indicators/indices. The exampleconfiguration of the plurality of sets may enable dynamicenabling/disabling of cross-carrier scheduling for the cell as furtherdescribed herein.

A base station may configure, for a first BWP set 2904, an initial BWP(e.g., BWP with BWP indicator/index 0), a default BWP (e.g., BWP withBWP indicator/index N) and a first BWP (BWP with BWP indicator/index P).P and the N may be less than K (e.g., K=4, or any other quantity). K maybe equal to a maximum quantity of BWPs in a BWP set. The wireless devicemay determine that the initial BWP, the default BWP and the first BWPbelong to the first BWP set 2904, for example, based on BWPindicator/indices of the initial BWP, the default BWP, and the first BWPbeing smaller than K. The base station may configure, for a second BWPset 2908 (e.g., a second BWP set, a second BWP (e.g., BWP with BWPindicator/index P+O). P+O may be greater than or equal to K (e.g., O=K).The wireless device may determine that the second BWP corresponds to thesecond BWP set 2908, for example, based on a second BWP index of thesecond BWP being greater than or equal to K. Offset O may be implicitlyor explicitly configured to be equal to K (or any other value). The basestation may configure/associate self-carrier scheduling for one or morefirst DL BWPs of the first BWP set 2904. The base station mayconfigure/associate cross-carrier scheduling for one or more second DLBWPs of the second BWP set 2908.

The wireless device may activate the first BWP of the first BWP set 2904(e.g., BWP with BWP indicator/index P) as an active BWP. The wirelessdevice may switch from the first BWP to the second BWP, for example,based on/in response to receiving a command activating/enablingcross-carrier scheduling for the cell. The wireless device may determinethe second BWP from the second BWP set 2908 based on the BWPindicator/index of an active BWP of the cell (e.g., the BWPindicator/index P of the first BWP), for example, based on/in responseto receiving the command/indication. The wireless device may determinethe second BWP based on determining a sum of the BWP indicator/index ofthe first BWP and the offset (e.g., P+O). The wireless device mayperform one or more operations related to cross-carrier scheduling inaccordance with the procedures described with reference to FIG. 28A-C.For example, the wireless device may determine search spaces of ascheduling cell, for cross-carrier scheduling of the cell, based onsearch spaces of the second BWP from the second BWP set 2908.

The first BWP set 2904 may comprise one or more first BWPsassociated/configured with self-carrier scheduling for a primary cell ofa cell group or a PUCCH group. The second BWP set 2908 may comprise oneor more second BWPs associated/configured with cross-carrier schedulingfor a secondary cell, for example, if the secondary cell is configuredwith cross-carrier scheduling.

A base station may configure a first UL BWP set and a second UL BWP set.The first UL BWP set may correspond to a first (DL) BWP set and thesecond UL BWP set may correspond to a second (DL) BWP set. Theconfiguration may be applied for unpaired spectrum or if an UL BWP ismapped to a DL BWP in terms of BWP switching. The base station mayconfigure a single UL BWP set regardless of a configured quantity of DLBWP sets. The base station may configure any other quantity of UL BWPsets. The wireless device may be configured with one or more UL BWPs(e.g., with UL BWP indicators/indices being less than K), for example,if the wireless device may implicitly determine the first BWP set andthe second BWP set based on a BWP indicator/index of a BWP (e.g., asdescribed with reference to FIG. 29 ). The wireless device may determinea corresponding UL BWP for an active DL BWP, where a BWP indicator/indexof the active DL BWP is greater than or equal to K by determining a newvalue of BWP indicator/index (e.g., the new value=the BWPindicator/index−O, or the BWP indicator/index−K). The wireless devicemay determine a paired DL BWP in a different BWP set or the first BWPset, and may use a BWP indicator/index of the paired DL BWP to determinethe corresponding UL BWP.

A base station may configure self-carrier scheduling or cross-carrierscheduling for a BWP (e.g., DL BWP, UL BWP) of a first cell. The basestation may configure self-carrier scheduling for a first BWP of thefirst cell. The base station may configure cross-carrier scheduling fora second BWP of the first cell. The base station may configure a crosscarrier scheduling configuration (e.g., CrossCarrierSchedulingConfig)for the second BWP. The first BWP and the second BWP may share a sameset of parameters, (e.g., a same bandwidth and a same numerology) exceptfor configurations of search spaces and indication of self/cross-carrierscheduling. The base station may switch between the first BWP and thesecond BWP to switch between self-carrier scheduling and cross-carrierscheduling for the first cell. The base station may expect a first delayfor switching between the first BWP and the second BWP. The base stationmay expect a second delay for switching between the first BWP and athird BWP. The first BWP and the third BWP may or may not have a samebandwidth and a same numerology. The first delay may be smaller than thesecond delay. A wireless device may report its capability correspondingto the first delay. The wireless device may report its capabilitycorresponding to the second delay. The first delay and the second delaymay be independent of each other.

A wireless device may be configured with a first DL BWP of a first cell.A base station may configure one or more first search spaces for thefirst DL BWP of the first cell. The one or more first search spaces maysupport self-carrier scheduling via the first DL BWP for the first cellregardless of whether self-carrier scheduling is enabled or across-carrier scheduling is enabled for the first cell. The base stationmay configure one or more second search spaces for the first DL BWP ofthe first cell. The one or more second search spaces may supportself-carrier scheduling via the first DL BWP, for example, ifself-carrier scheduling is enabled for the first cell. The base stationmay configure one or more third search spaces for the first DL BWP ofthe first cell. The one or more third search spaces may supportcross-carrier scheduling via the first DL BWP, for example, ifcross-carrier scheduling is enabled for the first cell. The wirelessdevice may monitor the one or more first search spaces and the one ormore second search spaces, for example, if self-carrier scheduling isenabled for the first cell and an active DL BWP is the first DL BWP. Thewireless device may monitor the one or more first search spaces and theone or more third search spaces, for example, if cross-carrierscheduling is enabled for the first cell and the active DL BWP is thefirst DL BWP. The enabling of the self-carrier or the cross-carrier maybe indicated via RRC, MAC CE and/or DCI signaling.

A base station may configure (e.g., via one or more RRC messages) afirst search space of a DL BWP of a first cell. The base station mayconfigure (e.g., via the one or more RRC messages) a second search spaceof the DL BWP of the first cell. The base station may configureself-carrier scheduling for the first search space. A wireless devicemay monitor the first search space for one or more DCIs. The one or moreDCIs may comprise resource assignments for the first cell. The basestation may configure cross-carrier scheduling for the second searchspace. The base station may configure a parameter (e.g.,crossCarrierScheduled) as enabled or disabled, for example, to configurecross-carrier scheduling for the second search space. The wirelessdevice may use a cross carrier scheduling configuration (e.g.,CrossCarrierSchedulingConfig) of the first cell to locate a schedulingcell for the first cell (e.g., for cross-carrier scheduling for thesecond search space), for example, if the parameter is enabled.

The base station may or may not enable cross-carrier scheduling for oneor more common search spaces. The base station may or may not enablecross-carrier scheduling for one or more wireless device-specific searchspaces. The base station may not enable cross-carrier scheduling for oneor more wireless device-specific search spaces, for example, if thewireless device is configured to monitor one or more fallback DCIs onthe one or more wireless device-specific search spaces. The wirelessdevice may monitor non-fallback DCIs in one or more search spaces of thescheduling cell for the first cell, for example, if the wireless deviceis configured with cross-carrier scheduling corresponding to the one ormore search spaces. The wireless device may not be configured withcross-carrier scheduling for a common search space. Cross-carrierscheduling may be applied for one or more wireless device-specificsearch spaces of a BWP of the first cell.

A base station may configure (e.g., via RRC signaling) a plurality of DLBWPs for a first cell. The first cell may be a primary cell of a cellgroup. A wireless device may be activated with an initial DL BWP,wherein the plurality of DL BWPs may not comprise the initial DL BWP.The wireless device may be activated with the initial DL BWP via aninitial access procedure or a random access procedure. The base stationmay configure one or more first search spaces for a first DL BWP, of theplurality of the DL BWPs of the first cell. The one or more first searchspaces may be configured with self-carrier scheduling. The one or morefirst search spaces may be common search spaces. The wireless device maydetermine that the common search spaces are self-carrier scheduled. Theone or more first search spaces may be wireless device-specific searchspaces. The base station may determine whether to apply self-carrierscheduling or cross-carrier scheduling for the one or more second firstspaces.

The base station may configure one or more second search spaces for thefirst DL BWP of the plurality of the DL BWPs of the first cell. The oneor more second search spaces may be configured with cross-carrierscheduling. The one or more second search spaces may be wirelessdevice-specific search spaces. The base station may determine whether toapply self-carrier scheduling or cross-carrier scheduling for the one ormore second search spaces.

A wireless device may monitor one or more search spaces of a schedulingcell for receiving downlink/uplink scheduling information for a cell(e.g., a primary cell). The wireless device may not monitor any searchspace via the cell, for example, if cross-carrier scheduling is enabledfor the cell. The base station may configure one or more search spacesspecific to the cell. The base station may configure a BFR search spacefor the cell or a search space for monitoring sidelink DCIs. Thewireless device may monitor the BFR search space and/or the search spacefor sidelink DCIs, via the scheduling cell, for example, ifcross-carrier scheduling is enabled for the cell. Monitoring the BFRsearch space and/or the search space for sidelink DCIs may degradeperformance of the wireless device. The wireless device may not be ableto determine a new beam based on a TCI state of the BFR searchspace/BFR-CORESET, for example, if the wireless device monitors the BFRsearch space via the scheduling cell. The wireless device may not beable to receive sidelink DCIs, for example, if the scheduling cell isinactive state. The wireless device may get interrupted due to switchingbetween scheduling via the cell (e.g., self-carrier scheduling) andscheduling via the scheduling cell (e.g., cross-carrier scheduling),resulting in service interruption. Various enhancements may be used forfacilitating self-carrier scheduling and cross-carrier scheduling of acell. A base station may indicate a search space, of the cell, as beingassociated with cross-carrier scheduling based on mapping the searchspace to another search space of a scheduling cell. The wireless devicemay determine a search space, of the cell, as being configured withself-carrier scheduling based on an indicator/index of the search spacenot being mapped to any indicator/index of one or more search spaces ofa scheduling cell. The wireless device may determine a search space asbeing configured with cross-carrier scheduling based on anindicator/index of the search space being mapped to another search spaceof a scheduling cell. Determination of whether a search space isconfigured with self-carrier scheduling or cross-carrier schedulingbased on mapping of search space indicators/indices may limitflexibility of the base station in determining/assigning search spaceindicators/indexes among multiple BWPs of the cell and the schedulingcell.

A base station may indicate, for each search space of a cell,self-carrier scheduling or cross-carrier scheduling. The base stationmay indicate self-carrier scheduling for a BFR search space. The basestation may indicate self-carrier scheduling for a common search space(e.g., for monitoring SIBs, RARs, paging signals). The base station mayindicate self-carrier scheduling for a search space for monitoringsidelink DCIs. The base station may indicate cross-carrier schedulingfor a wireless device-specific search space for monitoring non-fallbackDCIs. The base station may configure self-carrier scheduling orcross-carrier scheduling for the search spaces explicitly (e.g., via RRCsignaling, MAC-CE, etc.) such that the base station is not restricted inassigning search space indicators/indexes. The wireless device maymonitor one or more first search spaces of the cell, via the cell, basedon self-carrier scheduling. The wireless device may monitor one or moresecond search spaces of the cell, via the scheduling cell, based oncross-carrier scheduling. Indicating self-carrier scheduling orcross-carrier scheduling for each search space may allow efficientcross-carrier scheduling for the cell (e.g., a primary cell) enablingthe wireless device to perform various operations associated with cellbased on different search spaces.

FIG. 30 shows an example search space configuration of a search space.The search space configuration may be used to configure a search spacewith self-carrier scheduling or cross-carrier scheduling. A base stationmay send the search space configuration to the wireless device.

One or more parameters of a search space (e.g., configured for a DL BWPof the first cell) may comprise an indication (e.g.,CrossCarrierScheduled) to enable (e.g., configure) or disablecross-carrier scheduling for the search space, The one or moreparameters may indicate, for the search space, a quantity of candidates(e.g., PDCCH candidates) for each aggregation level (e.g.,nrofCandidates). The wireless device may use the indicated quantity ofcandidates for each aggregation level of the search space, for example,if cross-carrier scheduling is enabled/configured for the search space.The wireless device may monitor a second search space of a schedulingcell for the first cell, for example, if cross-carrier scheduling isenabled for the search space. The wireless device may use all theconfiguration parameters of the search space for monitoring one or moreDCIs (e.g., scheduling data for the first cell) via the search space,for example, if cross-carrier scheduling is disabled for the searchspace. The indication for enabling or disabling cross-carrier schedulingfor the search space may be available, for example, if the search spaceis a wireless device-specific search space and the first cell isconfigured with cross-carrier scheduling by the scheduling cell.

A parameter (e.g., ue-Specific-cross-carrier) may indicate DCI formatsof DCI to be monitored via a search space. The indication for enablingor disabling cross-carrier scheduling for a search space may bepresent/available in the search space configuration based on one or moreconsiderations. The indication for enabling or disabling cross-carrierscheduling for the search space may be available, for example, if thesearch space is a wireless device-specific search space, DCI formats(e.g., parameter dci-Formats) configured with the search space (e.g.,monitored for the search space) does not comprise fallback DCI (e.g.,one or more DCI formats configured for the search space comprisenon-fallback DCIs), and/or the first cell is configured withcross-carrier scheduling by the scheduling cell. DCI formatscorresponding to fallback DCIs may comprise DCI format 0_0/1_0 (e.g.,indicated by parameter formats0-0-And-1-0). Otherwise, the wirelessdevice may not be configured with the indication for enabling ordisabling cross-carrier scheduling for the search space. A parameter(e.g., controlResourceSetId) may indicate a CORESET associated with thesearch space.

The wireless device may not apply (or enable) cross-carrier schedulingfor a third search space of a DL BWP of the first cell, for example, ifone or more following conditions are being met. The one or moreconditions may comprise: the third search space being a wirelessdevice-specific search space, the third search space being configuredfor monitoring one or more DCIs based on non-fallback DCI formats (e.g.,DCI format 1_1, DCI format 0_1, DCI format 1_2, DCI format 0_2), a firstDL BWP of the first cell not being an initial DL BWP, the first DL BWPof the first cell not being configured as a default DL BWP, the firstcell being a primary cell of a cell group, the first cell being aprimary cell of a PUCCH group (e.g., a PUCCH Cell), the first cell notbeing configured with a carrier scheduling. The wireless device may notexpect that the indication for enabling or disabling cross-carrierscheduling for the search space to be available/configured for thesearch space, for example, if the one or more conditions are not met.

A wireless device may receive (e.g., from a base station) one or moremessages. The one or more messages may comprise configuration parametersfor a first cell. The configuration parameters may comprise across-carrier scheduling cell indicator (e.g., index, or identifier) andone or more first parameters of a first search space for monitoring oneor more first DCIs. The first DCIs may comprise/schedule resourceassignments/resources corresponding to data for the first cell. The oneor more first parameters may comprise a first search spaceindicator/index of the first search space. The configuration parametersmay comprise one or more second parameters of a second search space formonitoring one or more second DCIs. The one or more second DCIs maycomprise resource assignments corresponding to data for the first cell.The one or more second parameters may comprise a second search spaceindicator/index of the second search space and an indication of across-carrier scheduling.

The wireless device may determine a third search space, configured forthe scheduling cell, based on the one or more second parameters of thesecond search space of the first cell. The third search space may beconfigured for an active DL BWP of the scheduling cell. A third searchspace indicator/index of the third search space may be the same as thesecond search space indicator/index of the second search space. Thethird search space indicator/index of the third search space may beassociated with the second search space indicator/index of the secondsearch space. The association may be configured by the base station. Thethird search space indicator/index may be a sum of the second searchspace indicator/index and an offset value (e.g., the offset value=10, orany other value). The third search space may have a same order, amongone or more search spaces configured for the active DL BWP of thescheduling cell, as an order of the second search space among one ormore search spaces for an active DL BWP of the first cell. The basestation may indicate cross-carrier scheduling for the second searchspace based on the third search space indicator/index of the thirdsearch space being associated with the second search spaceindicator/index. The base station may indicate cross-carrier schedulingfor the second search space based on the third search spaceindicator/index of the third search space being the same as the secondsearch space indicator/index.

The wireless device may monitor the first search space of the first cellfor the one or more first DCIs. The wireless device may monitor thethird search space of the scheduling cell for the first cell for the oneor more second DCIs. The first search space may be indicated withself-carrier scheduling regardless of whether or not the second searchspace is enabled with cross-carrier scheduling.

The wireless device may receive a command (e.g., via MAC CE(s), and/orDCI(s)) activating cross-carrier scheduling for the first cell. Thecommand may be a MAC CE activating one or more secondary cells. The MACCE may indicate an activation of the scheduling cell. The command mayenable cross-carrier scheduling. The wireless device may activate thescheduling cell (e.g., if not already active), for example, based on/inresponse receiving the command. The wireless device may start monitoringthe third search space of the scheduling cell for the one or more secondDCIs, for example, based on/in response to receiving the command. Thewireless device may monitor the third search space for one or more thirdDCIs comprising resource assignments for the scheduling cell. The secondsearch space indicator/index may be larger than the first search spaceindex. A smallest indicator/index for the second search space may begreater than a highest indicator/index for the first search space. Thelowest indicator/index for the second search space may be 40 (e.g., orany other value).

A wireless device may determine self-carrier scheduling or cross-carrierscheduling for a search space of a DL BWP of a first cell based on asearch space indicator/index of the search space, for example, ifcross-carrier scheduling is enabled/configured for the first cell. Thewireless device may determine that the search space is configured withcross-carrier scheduling, for example, if search space indicator/indexis greater than or equal to M (e.g., M=10, 40, or any other value). Thewireless device may determine that the search space isconfigured/indicated with self-carrier scheduling, for example, ifsearch space indicator/index is smaller than M.

A wireless device may determine self-carrier scheduling or cross-carrierscheduling for a search space of a DL BWP of a first cell based on aCORESET associated with the search space, for example, if cross-carrierscheduling is enabled/configured for the first cell. The wireless devicemay determine that the search space is configured/indicated withself-carrier scheduling, for example, if the search space isassociated/configured with a first CORESET of the first cell (e.g.,controlResourceSetId is present and indicates the first CORESET of thefirst cell). The wireless device may determine the search space isconfigured/associated with cross-carrier scheduling, for example, if noCORESET is associated with the search space or if an invalid CORESETindicator is indicated (e.g., in controlResourceSetId).

FIG. 31A shows an example configuration of search spaces. The exampleconfiguration of search spaces may be used to indicate self-carrierscheduling or cross-carrier scheduling for a search space in a scheduledcell. The example configuration of search spaces may be used toimplicitly indicate search spaces of a scheduling cell to be used forcross-carrier scheduling of resources in the scheduled cell. A searchspace in a scheduling cell, that has a same search space indicator/indexas a search space in a scheduled cell, may be used to receive controlsignaling (e.g., indicating assignments in the scheduled cell). FIG. 31Band FIG. 31C show example methods at a base station and a wirelessdevice, respectively, for cross-carrier scheduling and self-carrierscheduling.

A base station may send (e.g., step 3132) configuration parameters to awireless device. The configuration parameters may indicate search spacesfor a first cell 3104 (e.g., scheduled cell, cell 0) and a second cell3108 (e.g., a scheduling cell, cell 1). The configuration parameters mayindicate, for each search space, one or more of the parameters asdescribed with reference to FIG. 30 . The configuration parameters mayindicate, for each search space, one or more of: DCI formats to bemonitored via the search space, whether the search space isconfigured/enabled with cross-carrier scheduling, monitoring occasionsassociated with the search space, a quantity of candidates (e.g., PDCCHcandidates) to be monitored for each CCE aggregation level (ALs), etc.

The base station may configure a first search space (e.g., with searchspace indicator/index 0), a second search space (e.g., with search spaceindicator/index i) and a third search space (e.g., with search spaceindicator/index j) for the first cell 3104. The base station mayconfigure a fourth search space (e.g., with search space indicator/indexi) for the second cell 3108. The wireless device may receive (e.g., step3152) the configuration parameters. The wireless device may determinethe fourth search space for the second cell 3108 corresponding to thesecond search space of the first cell 3104, for example, ifcross-carrier scheduling is enabled for the second search space and/orfor the first cell 3104. The wireless device may determine the fourthsearch space corresponding to the second search space based on thefourth search space and the second search space having a same searchspace indicator/index (e.g., i). The base station may configure fifthsearch space (e.g., with search space indicator/index k) and sixthsearch space (e.g., with search space indicator/index j) for the secondcell 3108. The wireless device may determine the sixth search space forthe second cell 3108 corresponding to the third search space of thefirst cell 3104, for example, if cross-carrier scheduling is enabled forthe third search space and/or for the first cell 3104. The wirelessdevice may determine the sixth search space corresponding to the thirdsearch space based on the sixth search space and the third search spacehaving a same search space indicator/index (e.g., j).

The wireless device may determine that cross-carrier scheduling isconfigured for the second search space of the first cell 3104 based onthe fourth search space of the second cell 3108 having a same searchspace indicator/index as the second search space of the first cell 3104.The wireless device may determine that cross-carrier scheduling isconfigured for the third search space of the first cell 3104 based onthe sixth search space of the second cell 3108 having a same searchspace indicator/index as the third search space of the first cell 3104.The wireless device may determine that cross-carrier scheduling isconfigured for the second search space of the first cell 3104 based onan indication (e.g., parameter CrossCarrierEnabled, or parameterCrossCarrierScheduled being set to true) associated with a configurationof the second search space. The wireless device may determine thatcross-carrier scheduling is configured for the third search space of thefirst cell 3104 based on an indication (e.g., parameterCrossCarrierEnabled) associated with a configuration of the third searchspace.

The base station may send (e.g., step 3136), via a search space of thefirst cell (e.g., the first search space), first DCI schedulingtransmission via the first cell. The wireless device may receive (e.g.,step 3154), via the search space of the first cell, the first DCIscheduling transmission via the first cell (e.g., comprising resourceassignment for the first cell). The base station 3108 may send (e.g.,step 3137), via the first cell, downlink data as scheduled by the firstDCI. The wireless device may subsequently receive (e.g., step 3156), viathe first cell and based on the resource assignment, downlink data.

The base station may send (e.g., step 3138) a commandenabling/activating cross-carrier scheduling for the first cell. Thebase station may send (e.g., step 3140), via a search space of thesecond cell (e.g., the fifth search space and/or the sixth searchspace), second DCI scheduling transmission via the first cell (e.g.,comprising resource assignment for the first cell). The wireless devicemay determine (e.g., step 3158) the search space of the second cell as asearch space corresponding to a search space of the first cell (e.g., asdescribed above). The wireless device may receive (e.g., step 3160), viathe search space of the second cell, the second DCI. The base station3108 may send (e.g., step 3142), via the first cell, downlink data asscheduled by the second DCI. The wireless device may subsequentlyreceive (e.g., step 3162), via the first cell and based on the resourceassignment, the downlink data.

FIG. 31D and FIG. 31E show an example method 3170 that may be performedby a base station and an example method 3182 that may be performed by awireless device, respectively. Steps 3172-3180 of FIG. 31D may besimilar to steps 3136-3142, respectively, as described with reference toFIG. 31B. Steps 3184-3192 of FIG. 31E may be similar to steps 3154-3162,respectively, as described with reference to FIG. 31C.

The wireless device may receive DCIs (e.g., the first DCI and/or thesecond DCI) based on monitoring the search spaces. The wireless devicemay monitor the first search space of the first cell regardless ofwhether or not cross-carrier scheduling is enabled/disabled. Thewireless device may or may not monitor the second search space or thethird search space, for example, based on the cross carrier schedulingbeing enabled. The wireless device may monitor the fourth search spaceand the sixth search space for receiving DCIs (e.g., comprising resourceassignments for the first cell), for example, if cross-carrierscheduling is enabled and based on the fourth search space correspondingto the second search space and the sixth search space corresponding tothe third search space. The wireless device may monitor the fourthsearch space based on configuration parameters of the fourth searchspace (e.g., DCI formats and/or monitoring occasions associated with thefourth search space). The wireless device may monitor the fourth searchspace based on configuration parameters of the second search space(e.g., DCI formats and/or aggregation levels associated with the secondsearch space). The wireless device may monitor the sixth search spacebased on configuration parameters of the sixth search space (e.g., DCIformats and/or monitoring occasions associated with the sixth searchspace). The wireless device may monitor the sixth search space based onconfiguration parameters of the third search space (e.g., DCI formatsand/or aggregation levels associated with the second search space). Thewireless device may determine candidates for receiving the DCIs via thefourth search space based on configuration parameters of the secondsearch space (e.g., ALs, candidates of the second search space). Thewireless device may determine candidates for receiving the DCIs via thesixth search space based on configuration parameters of the third searchspace (e.g., ALs, candidates of the third search space). The secondsearch space and the third search space may or may not be configuredwith other parameters (e.g., monitoring occasions and/or DCI formats).

FIG. 32 shows an example configuration of search spaces. The exampleconfiguration of search spaces may be used to implicitly indicateself-carrier scheduling or cross-carrier scheduling for a search spacein a scheduled cell. The example configuration of search spaces may beused to implicitly indicate search spaces of a scheduling cell to beused for cross-carrier scheduling of resources in the scheduled cell. Asearch space in a scheduling cell that is associated with a search spacein a scheduled cell may be used to determine resource assignments in thescheduled cell. The association may be based on an offset value.

A base station may configure (e.g., via one or more messages sent to awireless device) search spaces for a first cell 3204 (e.g., scheduledcell, cell 0) and a second cell 3208 (e.g., a scheduling cell, cell 1).The base station may send/indicate, to the wireless device, one or moreconfiguration parameters for each search space (e.g., as described abovewith reference to FIG. 31A).

The base station may configure a first search space (e.g., with searchspace indicator/index 0), a second search space (e.g., with search spaceindicator/index i+o) and a third search space (e.g., with search spaceindicator/index j+o) for the first cell 3204. The base station mayconfigure a fourth search space (e.g., with search space indicator/indexi) for the second cell 3208. The wireless device may determine thefourth search space of the second cell 3208 corresponding to the secondsearch space of the first cell 3204, for example, if cross-carrierscheduling is enabled for the second search space and/or for the firstcell. The wireless device may determine the fourth search spacecorresponding to the second search space based on the fourth searchspace being associated with the second search space (e.g., a searchspace indicator/index i of the fourth search space and a search spaceindicator i+o of the second search space being separated by a predefinedoffset value o). The base station may configure a fifth search space(e.g., with search space indicator/index k) and sixth search space(e.g., with search space indicator/index j) for the second cell. Thewireless device may determine the sixth search space of the second cell3208 corresponding to the third search space of the first cell 3204, forexample, if cross-carrier scheduling is enabled for the sixth searchspace and/or for the first cell. The wireless device may determine thesixth search space corresponding to the third search space based on thesixth search space being associated with the third search space (e.g., asearch space indicator/index j of the sixth search space and a searchspace indicator/index j+o of the second search space being separated bya predefined offset value o).

The wireless device may determine that cross-carrier scheduling isenabled for the second search space of the first cell 3204 based on thefourth search space of the second cell 3208 corresponding to the secondsearch space of the first cell 3204. The wireless device may determinethat cross-carrier scheduling is enabled for the third search space ofthe first cell 3204 based on the sixth search space of the second cell3208 corresponding to the third search space of the first cell 3204. Thewireless device may determine that cross-carrier scheduling is enabledfor the second search space of the first cell 3204 based on anindication (e.g., parameter CrossCarrierEnabled) associated with aconfiguration of the second search space. The wireless device maydetermine that cross-carrier scheduling is enabled for the third searchspace of the first cell 3204 based on an indication (e.g., parameterCrossCarrierEnabled) associated with a configuration of the third searchspace. The base station and/or the wireless device may perform variousoperations as described with reference to FIGS. 31A-C.

The wireless device may monitor the first search space of the first cellregardless of whether or not cross-carrier scheduling isenabled/disabled. The wireless device may or may not monitor the secondsearch space or the third search space. The wireless device may monitorthe fourth search space and the sixth search space for receiving DCIs(e.g., comprising resource assignments for the first cell), for example,if cross-carrier scheduling is enabled and based on the fourth searchspace corresponding to the second search space and the sixth searchspace corresponding to the third search space. The wireless device maymonitor the fourth search space based on configuration parameters of thefourth search space (e.g., DCI formats and/or monitoring occasionsassociated with the fourth search space). The wireless device maymonitor the fourth search space based on configuration parameters of thesecond search space (e.g., DCI formats and/or aggregation levelsassociated with the second search space). The wireless device maymonitor the sixth search space based on configuration parameters of thesixth search space (e.g., DCI formats and/or monitoring occasionsassociated with the sixth search space). The wireless device may monitorthe sixth search space based on configuration parameters of the thirdsearch space (e.g., DCI formats and/or aggregation levels associatedwith the second search space). The wireless device may determinecandidates for receiving the DCIs via the fourth search space based onconfiguration parameters of the second search space (e.g., ALs,candidates of the second search space). The wireless device maydetermine candidates for receiving the DCIs via the sixth search spacebased on configuration parameters of the third search space (e.g., ALs,candidates of the third search space). The second search space and thethird search space may or may not be configured with other parameterssuch as monitoring occasions and/or DCI formats.

A wireless device may receive one or more messages. The one or moremessages may comprise configuration parameters for a first cell. Theconfiguration parameters may comprise a cross-carrier scheduling cellindex/identifier and one or more first parameters of a first searchspace for monitoring one or more first DCIs. The first DCIs maycomprise/schedule resource assignments/resources corresponding to dataassociated with the first cell. The one or more first parameters maycomprise a first search space indicator/index. The configurationparameters may comprise one or more second parameters of a second searchspace for monitoring one or more second DCIs. The one or more secondDCIs may comprise resource assignments corresponding to data associatedwith the first cell. The one or more second parameters may comprise asecond search space indicator/index and an indication of a cross-carrierscheduling.

The wireless device may monitor the first search space of the first celland the second search space of the cell, for example, if cross-carrierscheduling is not enabled (e.g., during an initial access procedure,before BWP switching, before receiving a command activatingcross-carrier scheduling, before a scheduling cell is being activated).

The wireless device may receive a command (e.g., MAC CE(s), and/orDCI(s)) activating cross-carrier scheduling for the first cell. Thecommand may be a MAC CE activating one or more secondary cells. The MACCE may indicate an activation of the scheduling cell. The command mayenable the cross-carrier scheduling. The wireless device may activatethe scheduling cell (e.g., if not already activated), for example, basedon receiving the command. The wireless device may determine a thirdsearch space of the scheduling cell based on the second search spaceindicator/index, for example, based on receiving the command. A thirdsearch space indicator/index of the third search space may be the sameas the second search space indicator/index of the second search space.The wireless device may continue monitoring the first search space ofthe first cell for the one or more first DCIs. The wireless device maystop monitoring the second search space of the first cell. The wirelessdevice may start monitoring the third search space of the schedulingcell for the one or more second DCIs.

FIG. 33 shows an example configuration of search spaces. The exampleconfiguration of search spaces may be used to implicitly indicateself-carrier scheduling or cross-carrier scheduling for a search spacein a scheduled cell. One or more parameters configured for the searchspace in the scheduled cell may be used for receiving resourceassignment information via a search space in the scheduling cell. One ormore procedures associated with FIG. 33 may be similar to proceduresdescribed above with reference to FIGS. 31 and 32 .

A base station may configure (e.g., via one or more messages sent to awireless device) search spaces for a first cell 3304 (e.g., scheduledcell, cell 0) and a second cell 3308 (e.g., a scheduling cell, cell 1).The base station may send/indicate, to the wireless device, one or moreconfiguration parameters for each search space (e.g., as described abovewith reference to FIG. 31A).

The base station may configure a first search space (e.g., with searchspace indicator/index 0), a second search space (e.g., with search spaceindicator/index i) and a third search space (e.g., with search spaceindicator/index j) for the first cell 3304. The base station mayconfigure a fourth search space (e.g., with search space indicator/indexi). The wireless device may determine the fourth search spacecorresponding to the second search space of the first cell 3304, forexample, if cross-carrier scheduling is enabled for the second searchspace and/or the first cell 3304. The wireless device may determine thefourth search space corresponding to the second search space based onthe fourth search space and the second search space having a same searchspace indicator/index (e.g., i). The base station may configure a fifthsearch space (e.g., with search space indicator/index k) and a sixthsearch space (e.g., with search space indicator/index j) for the secondcell 3308. The wireless device may determine the sixth search space forthe second cell 3308 corresponding to the third search space of thefirst cell 3304, for example, if cross-carrier scheduling is enabled forthe third search space and/or the first cell 3304. The wireless devicemay determine the sixth search space corresponding to the third searchspace based on the sixth search space and the third search space havinga same search space indicator/index (e.g., j).

The wireless device may determine that cross-carrier scheduling isconfigured for the second search space of the first cell 3304 based onthe fourth search space of the second cell 3308 corresponding to thesecond search space of the first cell 3304. The wireless device maydetermine that cross-carrier scheduling is configured for the thirdsearch space of the first cell 3304 based on the sixth search space ofthe second cell 3308 corresponding to the third search space of thefirst cell 3304. The wireless device may determine that cross-carrierscheduling is configured for the second search space of the first cell3304 based on an indication (e.g., parameter CrossCarrierEnabled)associated with a configuration of the second search space. The wirelessdevice may determine that cross-carrier scheduling is configured for thethird search space of the first cell 3304 based on an indication (e.g.,parameter CrossCarrierEnabled) associated with a configuration of thethird search space. The base station and/or the wireless device mayperform various operations as described with reference to FIGS. 31B and31C.

Various examples described herein (e.g., with reference to FIGS. 26-33 )may be applied for scheduling downlink transmissions or uplinktransmissions. With reference to FIG. 26A, for example, the DCI (e.g.,DCI-1 2612 or DCI-2 2622) may schedule resources for either a downlinktransmission or an uplink transmission.

The wireless device may monitor the first search space of the first cellregardless of whether or not cross-carrier scheduling isenabled/disabled. The wireless device may monitor the second searchspace and the third search space based on configuration parametersindicated by the base station, for example, if self-carrier schedulingis enabled. The wireless device may monitor the fourth search space andthe sixth search space for receiving DCI messages comprising resourceassignments for the first cell, for example, if cross-carrier schedulingis enabled and based on the fourth search space corresponding to thesecond search space and the sixth search space corresponding to thethird search space. The wireless device may or may not stop monitoringthe second search space and the third search space, for example, ifcross-carrier scheduling is enabled.

The wireless device may continue monitoring the first search space, thesecond search space, and the third search space, for example, even ifcross-carrier scheduling is enabled. The wireless device mayadditionally monitor the fourth search space and the sixth search spacefor receiving DCI messages for the first cell, for example, ifcross-carrier scheduling is enabled.

The wireless device may determine candidates for receiving the DCImessages via the fourth search space based on one or more configurationparameters of the second search space (e.g., ALs, candidates of thesecond search space). The wireless device may determine candidates forreceiving the DCI messages via the sixth search space based on one ormore configuration parameters of the third search space (e.g., ALs,candidates of the third search space). The second search space and thethird search space may or may not be configured with other parameters(e.g., monitoring occasions and/or DCI formats).

FIG. 34A shows an example method for self-carrier scheduling andcross-carrier scheduling based on configuration of BWP sets. The examplemethod 3400 may be performed by a wireless device. At step 3404, thewireless device may receive an indication of first set of BWPs and asecond set of BWPs for a first cell. The first set of BWPs may beconfigured for self-carrier scheduling and the second set of BWPs may beconfigured for cross-carrier scheduling.

At step 3408, the wireless device may receive cross-carrier schedulingconfiguration for the second set of BWPs. The cross-carrier schedulingconfiguration may indicate a scheduling cell for the first cell. At step3412, the wireless device may activate a BWP from the first set of BWPs.The wireless device may activate the BWP from the first set of BWPs, forexample, based on receiving an indication from the base station. Thewireless device may perform self-carrier scheduling for the first cellbased on the activated BWP.

At step 3416, the wireless device may determine whether an indication toenable cross-carrier scheduling of the activated BWP is received (e.g.,from the base station). The indication may be DCI, a MAC CE, or an RRCconfiguration message. The indication may be a command activating ascheduling cell. The indication may be a command to switch tocross-carrier scheduling for the activated BWP. At step 3420, thewireless device may continue self-carrier scheduling for the first cell,for example, if the wireless device determines that the indication toenable cross-carrier scheduling is not received.

At step 3424, the wireless device may determine a second BWP from thesecond set of BWPs, for example, if the wireless device determines thatthe indication to enable cross-carrier scheduling is received. Thesecond BWP may have a same BWP indicator/index as the activated BWP(e.g., as described with reference to FIG. 28 ). The second BWP may havea BWP indicator/index that is equal to a sum of a BWP indicator/index ofthe first BWP and an offset value (e.g., as described with reference toFIG. 29 ). At step 3428, the wireless device may activate the second BWPfrom the second set of BWPs. At step 3432, the wireless device mayenable cross-carrier scheduling for the first cell. The wireless devicemay determine one or more second search spaces of the scheduling cellbased on one or more first search spaces of the second BWP. The wirelessdevice may determine the one or more second search spaces, wherein asecond search space indicator/index of a second search space of the oneor more second search spaces is same as a first search spaceindicator/index of a first search space of the one or more first searchspaces. The wireless device may monitor the one or more second searchspaces to receive control information scheduling resources in the firstcell.

FIG. 34B shows an example method for self-carrier scheduling andcross-carrier scheduling. The example method 3450 may be performed by awireless device. Steps 3454-3474 of FIG. 34B may be similar to steps3412-3432, respectively, as described with reference to FIG. 34A.

FIG. 35A shows an example method of self-carrier scheduling andcross-carrier scheduling based on configuration of search spaces. Theexample method 3500 may be performed by a wireless device. At step 3504,the wireless device may receive a cross-carrier scheduling configurationfor a cell. The cross-carrier scheduling configuration may comprise anindicator of a scheduling cell for the cell. At step 3508, the wirelessdevice may receive a first search space configuration for the cell. Thefirst search space configuration may be associated with a first searchspace configured for self-carrier scheduling. The first search spaceconfiguration may comprise an indicator of the first search space. Atstep 3512, the wireless device may receive a second search spaceconfiguration for the cell. The second search space configuration may beassociated with a second search space configured/enabled withcross-carrier scheduling. The second search space configuration maycomprise an indicator of the second search space. The second searchspace configuration may also comprise an indicator of a scheduling cell.

At step 3516, the wireless device may determine whether cross-carrierscheduling is enabled/activated for the cell. The wireless device maydetermine that cross-carrier scheduling is enabled based on receiving anindication. The indication may be DCI, a MAC CE, or an RRC configurationmessage. The indication may be a command activating the scheduling cell.

At step 3520, the wireless device may monitor the first search space ofthe first cell, for example, based on determining that cross-carrierscheduling is not enabled. The wireless device may additionally monitorthe second search space of the first cell, for example, based ondetermining that cross-carrier scheduling is not enabled.

At step 3524, the wireless device may determine a third search space ofthe scheduling cell based on the indicator of the second search space,for example, based on determining that cross-carrier scheduling is notenabled. An indicator of the third search space may be the same as theindicator of the second search space. A value of an indicator of thethird search space may be separated from a value of an indicator of thesecond search space by an offset value.

At step 3528, the wireless device may monitor the first search space ofthe first cell, for example, based on determining that cross-carrierscheduling is enabled. The wireless device may monitor the third searchspace of the scheduling cell, for example, based on determining thatcross-carrier scheduling is enabled.

FIG. 35B shows an example method for self-carrier scheduling andcross-carrier scheduling. The example method 3550 may be performed by awireless device. Steps 3558-3578 of FIG. 35B may be similar to steps3508-3528, respectively, as described with reference to FIG. 35A.

FIG. 36 shows an example method for determining whether a DL BWP of aprimary cell is configured with self-carrier scheduling or cross-carrierscheduling. The example method 3600 may be performed by a wirelessdevice. At step 3604, the wireless device may receive configurationparameters for the DL BWP of the primary cell. The configurationparameters may indicate search space configurations (e.g., as describedwith reference to FIG. 30 ) for a plurality of search spaces in the DLBWP. The search space configurations may indicate one or more wirelessdevice-specific search spaces. The configuration parameters mayindicate/comprise one or more CORESETs of the DL BWP.

At step 3612, the wireless device may determine that the DL BWP isconfigured with self-carrier scheduling, for example, based on awireless device-specific search space of the one or more wirelessdevice-specific search spaces being associated with a CORESET of the oneor more CORESETs. The wireless device may determine that wirelessdevice-specific search space is associated with the CORESET based on anindication in the search space configuration (e.g., parametercontrolResourceSetId). At step 3620, the wireless device may monitor asearch space of the DL BWP for DCIs (e.g., scheduling resources of theprimary cell) based on determining that the DL BWP is configured withself-carrier scheduling.

At step 3616, the wireless device may determine that the DL BWP isconfigured with cross-carrier scheduling, for example, based on none ofthe one or more wireless device-specific search spaces being associatedwith any CORESET of the one or more CORESETs. The wireless device maydetermine that the DL BWP is configured with cross-carrier scheduling,for example, based on none of the CORESET indicators associated with thewireless device-specific search spaces being the same as a CORESETindicator of the one or more CORESETs. The wireless device may determinethat a wireless device-specific search space is not associated with anyCORESET of the one or more CORESETs, for example, if the search spaceconfiguration does not comprise a parameter (e.g., controlResourceSetIdor a controlResourceSetId) being set to a predetermined value (e.g., 4,or any other value). At step 3624, the wireless device may monitor asearch space of a scheduling cell for DCIs (e.g., scheduling resourcesof the primary cell) based on determining that the DL BWP is configuredwith cross-carrier scheduling.

A wireless device may receive one or more messages. The one or moremessages may comprise configuration parameters for a first cell. Theconfiguration parameters may indicate one or more first DL BWPsindicated/configured with self-carrier scheduling, one or more second DLBWPs indicated/configured with cross-carrier scheduling, and ascheduling cell indicator/index for cross-carrier scheduling. Thewireless device may activate the first DL BWP of the one or more firstDL BPWs as an active DL BWP of the first cell. The wireless device mayreceive a command activating cross-carrier scheduling for the firstcell. The wireless device may determine a second DL BWP of the one ormore second DL BWPs based on a first BWP indicator/index of the first DLBWP. The wireless device may switch to the second DL BWP of the one ormore second DL BWPs as the active DL BWP of the first cell.

A wireless device may receive one or more messages. The one or moremessages may comprise configuration parameters for a first cell. Theconfiguration parameters may indicate a first BWP configured with afirst BWP indicator/index, a second BWP configured with a second BWPindicator/index, and a scheduling cell indicator/index for cross-carrierscheduling. The wireless device may activate the first DL BWP as anactive DL BWP of the first cell. The wireless device may receive acommand activating cross-carrier scheduling for the first cell. Thewireless device may determine the second DL BWP based on a first BWPindicator/index of the first DL BWP. The wireless device may switch tothe second DL BWP as the active DL BWP of the first cell.

A wireless device may receive one or more messages. The one or moremessages may comprise configuration parameters for a first cell. Theconfiguration parameters may comprise a cross-carrier scheduling cellindicator/index. The configuration parameters may comprise one or morefirst parameters of a first search space (e.g., for monitoring one ormore first DCIs comprising resource assignments of data for the firstcell). The one or more first parameters may comprise a first searchspace indicator/index. The configuration parameters may comprise one ormore second parameters of a second search space (e.g., for monitoringone or more second DCIs comprising resource assignments of data for thefirst cell) The one or more second parameters may comprise a secondsearch space indicator/index and an indication of cross-carrierscheduling. The wireless device may determine a third search space ofthe scheduling cell based on the one or more second parameters of thesecond search space of the first cell. The wireless device maymonitor/receive the one or more first DCIs via the first search space ofthe first cell. The wireless device may monitor/receive the one or moresecond DCIs via the third search space of the scheduling cell.

A wireless device may receive one or more messages. The one or moremessages may comprise configuration parameters for a first cell. Theconfiguration parameters may comprise a cross-carrier scheduling cellindicator/index. The configuration parameters may comprise one or morefirst parameters of a first search space (e.g., for monitoring one ormore first DCIs comprising resource assignments of data for the firstcell). The one or more first parameters may comprise a first searchspace indicator/index. The configuration parameters may comprise one ormore second parameters of a second search space (e.g., for monitoringone or more second DCIs comprising resource assignments of data for thefirst cell). The one or more second parameters may comprise a secondsearch space indicator/index and an indication of cross-carrierscheduling. The wireless device may monitor the first search space andthe second search space of the first cell. The wireless device mayreceive a command activating cross-carrier scheduling for the firstcell. The wireless device may determine a third search space of thescheduling cell based on the one or more second parameters of the secondsearch space of the first cell, for example, based on receiving thecommand. The wireless device may continue monitoring the one or morefirst DCIs via the first search space of the first cell. The wirelessdevice may stop monitoring the second search space of the first cell.The wireless device may start monitoring the one or more second DCIs viathe third search space of the scheduling cell.

A base station may configure cross-carrier scheduling for a first cellfor a wireless device. The base station may configure a second cell as ascheduling cell for the first cell. The wireless device may applycross-carrier scheduling for the first cell, for example, based on thecross-carrier scheduling configuration. The wireless device may notmonitor search spaces (e.g., wireless device-specific search spaces) ofthe first cell, for example, based on the wireless device performingcross-carrier scheduling for the first cell. Low frequency spectrum(e.g., below 6 GHz, or any other low frequency spectrum) may be criticalfor providing increased network coverage for some types ofcommunications (e.g., communications associated with 5G or 6Gcommunication standards, or other communications that use higherfrequency spectrum). For example, the first cell may be associated witha communication type that uses low frequency spectrum.

Communication via low frequency spectrum may necessitate dynamicspectrum sharing among different types of communications (e.g.,communications associated with different generations or different radioaccess technologies (RATs), such as LTE and 5G; LTE and NR; and/or 3G,4G, and 5G. A first type of communication (e.g., a first RAT, such asNR) may not necessarily be able to use low frequency spectrum based ondynamic spectrum sharing because of existing usage by a second type ofcommunication (e.g., a second RAT, such as LTE). The first type ofcommunication may be able to use the low frequency spectrum only if thesecond type of communication is not using the low frequency spectrum.Availability of resources for the first type of communication mayfluctuate based on usage by the second type of communication.Non-availability and/or fluctuating availability of resources (e.g.,associated with low frequency spectrum) for the first type ofcommunication may lead to performance degradation of the first type ofcommunication. Performance degradation may be more severe for controlchannels as control channel transmissions are mostly periodic, whereasresources for the control channels may only be available intermittently.Dynamic resource allocations for control channel transmissions may benecessary for an efficient spectrum sharing.

A base station may configure cross-carrier scheduling for a primary cellvia configuration messages (e.g., RRC signaling). A scheduling cell(e.g., a secondary) cell may be configured. The scheduling cell may beactive or inactive at a time of configuration. The wireless device maynot monitor the scheduling cell until the scheduling cell becomesactive, for example, if the scheduling cell is inactive at a time ofconfiguration. The base station may not be able to send/transmit, viathe scheduling cell, scheduling control information (e.g., DCI) for theprimary cell until the scheduling cell becomes active. The wirelessdevice may be unable to receive scheduling information via thescheduling cell, for example, if control channel resources of thescheduling cell are occupied for other communications. Inability toreceive control information via the scheduling cell may lead to serviceinterruption at the primary cell. The primary cell may be reconfiguredwith self-carrier scheduling, for example, if the scheduling cellbecomes deactivated. Reconfiguration may result in high latency (e.g.,because of high latency associated with transmission of configurationmessages, such as semi-static RRC messages). The wireless device may notbe able to receive scheduling DCIs for the primary cell, for example, ata time at which the reconfiguration is occurring.

A base station and a wireless device may enable or disable cross-carrierscheduling of a primary cell based on dynamic signaling (e.g., a MAC CEor DCI). The MAC CE may comprise an SCell activation/deactivation MACCE. The MAC CE and/or DCI may explicitly indicate enabling or disablingcross-carrier scheduling of the primary cell. The MAC CE and/or DCI maycomprise a scheduling cell indicator/index of a scheduling cell of theprimary cell, such that the scheduling cell may be dynamically adaptedamong one or more secondary cells available to the wireless device.Using dynamic scheduling may allow fast adaptation ofcross-carrier/self-carrier scheduling of the primary cell based onvarious factors. The various factors may comprise one or more of atraffic pattern for the primary cell, channel conditions of the primarycell, status of the scheduling cell (e.g., whether the scheduling cellis active or inactive), a status of CA (e.g., whether CA is activated ornot). Using dynamic scheduling may enable the base station todynamically change a scheduling cell for the primary cell (e.g., basedon an active BWP of a secondary cell (e.g., no dormant secondary cell isconfigured as the scheduling cell), based on a channel condition of thesecondary cell, based on congestion level of the secondary cell). Thewireless device may apply self-carrier scheduling for the primary cellbased on the cross-carrier scheduling being disabled. The wirelessdevice may apply cross-carrier scheduling for the primary cell based onthe cross-carrier scheduling being enabled.

A base station may configure cross-carrier scheduling for a first cell.The first cell may be associated with a first type of communication(e.g., a first RAT) that may share frequency spectrum with a second cellassociated with a second type of communication (e.g., a second RAT). Thebase station may dynamically indicate a scheduling cell via MAC CE(s)and/or DCI(s). The base station may indicate enabling of cross-carrierscheduling and determining the scheduling cell, for example, if thefirst cell does not have sufficient control channel resources. The basestation may determine the scheduling cell that has a sufficient quantityof control channels with good channel qualities. Indication of thescheduling cell, via semi-static signaling (e.g., RRC signaling), maynot efficiently reflect dynamic changes of resource availability andchannel qualities. Various examples described herein may allow the basestation to dynamically select (e.g., determine and/or update) ascheduling cell for the first cell based on the resource availabilityand/or the channel quality of both the scheduling cell and the firstcell.

A wireless device may dynamically switch between self-carrier schedulingand cross-carrier scheduling. The wireless device may dynamically switchbetween self-carrier scheduling and cross-carrier scheduling, forexample, without receiving an explicit command to indicate theswitching. A wireless device may receive one or more configurationmessages (e.g., RRC messages). The configuration messages may compriseconfiguration parameters. The configuration parameters may comprise anindication of cross-carrier scheduling for a first cell, a first searchspace of a first cell, and a second search space of a second cell. Thesecond cell may be a scheduling cell for the first cell if cross-carrierscheduling is used/enabled for the first cell. The wireless device maydetermine between self-carrier scheduling and cross-carrier schedulingbased on the first search space, the second search space, and/or anactivation status of the second cell. The wireless device may determinethat the second cell is not activated at a first time (e.g., in a firstslot). The wireless device may determine to use self-carrier based ondetermining that the second cell is not activated. The wireless devicemay monitor the first search space of the first cell for receiving firstDCI (e.g., comprising resource assignments for the first cell), forexample, based on the second cell not being activated. The wirelessdevice may determine, at a second time (e.g., in a second slot), thatmonitoring occasions associated with the first search space are notvalid (e.g., based on slot format indication of the first cell). Thewireless device may not be able to monitor the first search space, forexample, based on determining that the monitoring occasions associatedwith the first search space are not valid. The wireless device mayuse/switch to cross-carrier scheduling based on determining that themonitoring occasions associated with the first search space are notvalid. The wireless device may monitor the second search space of thesecond cell for receiving second DCI (e.g., comprising resourceassignments for the first cell), for example, based on determining thatthe monitoring occasions associated with the first search space are notvalid. Various examples described herein allow dynamic switching betweenself-carrier and a cross-carrier scheduling without increasing wirelessdevice complexity.

A wireless device may perform cross-carrier scheduling for a first cell,for example, if the cross-carrier scheduling is enabled for the firstcell. The wireless device may continue performing self-carrierscheduling for the first cell in addition to cross-carrier scheduling.Various examples herein allow additional control channelresources/capacity, based on cross-carrier scheduling, without impactingon control channel resources/capacities of self-carrier scheduling.First DCI may be sent/transmitted via a second cell to scheduleresources for the first cell. The wireless device may determine a firstDCI size of the first DCI based on a second DCI size of second DCI forthe second cell. The second cell may be a scheduling cell for the firstcell, for example, if cross-carrier scheduling is enabled. The first DCIsize may be based on one or more first DCI formats and the second DCIsize. The one or more first DCI formats may be determined based on oneor more parameters configured for the first cell. The second DCI sizemay be based on one or more second DCI formats. The one or more secondDCI formats may be determined based on one or more parameters configuredfor the second cell. The first DCI may comprise resource assignments forthe first cell. The second DCI may comprise resource assignments for thesecond cell. A first RNTI and a second RNTI may be used for the firstDCI and the second DCI, respectively, to differentiate between the firstDCI and the second DCI. Various examples herein allow increased controlchannel capacity without substantially increasing wireless devicecomplexity.

A wireless device may monitor a first search space of a first cell, forexample, based on one or more first conditions being met. The wirelessdevice may monitor a second search space of a second cell forcross-carrier scheduling of the first cell. The wireless device maymonitor the second search space based on one or more second conditionsbeing met. The wireless device may monitor the first search space forfirst DCI. The first DCI may comprise resource assignments for the firstcell. The wireless device may monitor the second search space of thesecond cell for second DCI, The second DCI may comprise resourceassignments for the first cell. The one or more first conditions maycomprise that the first DCI is scrambled with a first RNTI. The one ormore first conditions may comprise that the first DCI is based on one ormore first DCI formats. The one or more first conditions may comprisethat at least a monitoring occasion of the first search space isconfigured in one or more downlink OFDM symbols of a first slot. Thewireless device may monitor the monitoring occasion of the first searchspace in the first slot. The one or more second conditions may comprisethat the second DCI is scrambled with a second RNTI. The one or moresecond conditions may comprise that the second DCI is based on one ormore second DCI formats. The one or more second conditions may comprisethat no monitoring occasion of the first search space is valid (e.g.,configured over the one or more downlink OFDM symbols) in the firstslot. The wireless device may monitor the second search space for thefirst cell in the first slot. The first RNTI may be a C-RNTI. The secondRNTI may be configured by the base station, and may be different fromthe first RNTI (e.g., C-RNTI). The one or more first DCI formats maycomprise fallback DCI formats. The one or more second DCI formats maycomprise non-fallback DCI formats.

A wireless device may receive one or more configuration messages (e.g.,RRC messages). The one or more RRC messages may comprise configurationparameters related to cross-carrier scheduling for a first cell. Theconfiguration parameters may comprise a scheduling cell indicator/index(e.g., an indicator/index of a second cell). The configurationparameters may comprise a second RNTI used for cross-carrier scheduling.The wireless device may receive a first RNTI (e.g., C-RNTI), from a basestation, for example, via an initial access procedure. The second RNTI,used for the cross-carrier scheduling, may be configured by the basestation. The wireless device may monitor a first search space of thefirst cell for first DCI. The first DCI may comprise resourceassignments for the first cell. The base station may activatecross-carrier scheduling. Cross-carrier scheduling may be activated, forexample, if the base station activates the second cell. The base stationmay send/transmit an indication (e.g., via MAC CE(s) and/or DCI(s))enabling the cross-carrier scheduling. The wireless device may monitor asecond search space of the second cell for second DCI, for example,based on/in response to the activation of cross-carrier scheduling. Thesecond DCI may comprise resource assignment for the first cell.

The wireless device may continue monitoring the first search space forthe first DCI, for example, if cross-carrier scheduling is enabled. Thewireless device may monitor the first search space for the first DCIthat is scrambled based on the first RNTI. The wireless device maymonitor the second search space for the second DCI that is scrambledbased on the second RNTI.

The first DCI may be based on a first DCI format (e.g, DCI format1_0/0_0, a fallback DCI format). The first DCI may be based on a DCIformat 1_1/0_1 (e.g., a non-fallback DCI format) and/or DCI format1_2/0_2 (e.g., a compact DCI format). One or more DCI fields of the DCIformat for the first DCI may be determined based on one or moreconfiguration parameters for the first cell. A DCI field indicating afrequency resource allocation may be determined based on an active DL/ULBWP of the first cell. A DCI field indicating a time domain resourceallocation may be determined based on one or more time-domain resourceallocation entries (pre)-configured for the first cell. The second DCImay or may not be based on a fallback DCI format (e.g., DCI format1_0/0_1). The second DCI may be based on a second DCI format (e.g., anon-fallback DCI format, such as DCI format 1_1/0_1 and/or a compact DCIformat, such as DCI format 1_2/0_2). The wireless device may or may notmonitor any DCI based on the fallback DCI format based on cross-carrierscheduling.

One or more first DCI fields of a second DCI format for the second DCImay be determined based on the one or more configuration parameters forthe first cell. A DCI field, of the one or more first DCI fields for thesecond DCI, indicating frequency resource allocation may be determinedbased on the active DL/UL BWP of the first cell. The wireless device maydetermine a first DCI size of the second DCI based on the determiningthe one or more first DCI fields, The wireless device may monitor thesecond search space of the second cell for the second DCI.

The wireless device may monitor the second search space of the secondcell for third DCI. The third DCI may comprise resource assignments forthe second cell. The wireless device may perform, via the second searchspace, self-carrier scheduling for the second cell and cross-carrierscheduling for the first cell. The wireless device may determine one ormore second DCI fields of the third DCI based on one or more secondconfiguration parameters for the second cell. A frequency domainallocation DCI field of the third DCI may be determined based on anactive DL/UL BWP of the second cell. The wireless device may determine asecond DCI size of the second DCI based on the determining the one ormore second DCI fields.

The wireless device may compare the first DCI size and the second DCIsize. The wireless device may determine a third DCI size wherein thethird DCI size may be a larger DCI size among the first DCI size and thesecond DCI size. The wireless device may add padding bits (e.g., zeros)to the second DCI (or the second DCI format) if the second DCI size issmaller than the first DCI size. The wireless device may add zeros tothe third DCI (or a DCI format for the third DCI) if the second DCI sizeis smaller than the first DCI size. Addition of padding bits may alignDCI sizes between DCIs, sent via the second search space of the secondcell, for self-carrier scheduling and cross-carrier scheduling. Thethird DCI may be scrambled with the first RNTI. The second DCI may bescrambled with the second RNTI.

FIG. 37A shows an example of switching between self-carrier schedulingand cross-carrier scheduling for a cell. A base station 3704 mayactivate cross-carrier scheduling for a cell. Different indicators(e.g., RNTIs) may be used to differentiate between control signalsassociated with cross-carrier scheduling and self-carrier scheduling.FIG. 37B and FIG. 37C show example methods at the base station 3704 andthe wireless device 3708, respectively, for cross-carrier andself-carrier scheduling.

The base station 3704 may send (e.g., step 3732), to the wireless device3708, one or more parameters for cross-carrier scheduling (e.g.,cross-carrier configuration 3710) for a first cell (e.g., primary cell,cell 0). The one or more parameters may be sent via RRC signaling. Theone or more parameters may comprise an indication of cross-carrierscheduling. The one or more parameters may comprise a second RNTI. Thesecond RNTI may be used for DCI, comprising resource assignments for thefirst cell, as sent/transmitted via one or more search spaces of ascheduling cell for the first cell (e.g., a second cell, Cell 1). Theone or more parameters may comprise a scheduling cell indicator (e.g.,index or identifier). The scheduling cell indicator for cross-carrierscheduling may be updated via MAC CE(s) and/or DCI(s). The wirelessdevice may receive (e.g., step 3752) the one or more parameters.

The wireless device 3708 may operate using self-carrier scheduling forthe first cell, for example, until the wireless device 3708 receives acommand to activate cross-carrier scheduling for the first cell. Thebase station 3704 may send (e.g., step 3740), via a first search space(e.g., SS1) of the first cell, first DCI (e.g., DCI-1 3712). As furtherdescribed herein the first DCI may be based on (e.g., scrambled with) afirst RNTI. The first DCI may comprise resource assignments for downlinkdata 3714 for the first cell. The wireless device 3708 may receive(e.g., step 3760), via the first search space of the first cell, thefirst DCI. The base station 3704 may send (e.g., step 3742), via thefirst cell and based on the assigned resources indicated by the firstDCI, the downlink data 3714. The wireless device 3708 may receive (e.g.,step 3762), via the first cell and based on the assigned resourcesindicated by the first DCI, the data 3714.

The base station 3704 may send (e.g., step 3734), to the wireless device3708, a command 3716 to activate cross-carrier scheduling for the firstcell. The command may be a MAC CE or DCI. The command may be an SCellactivation/deactivation MAC CE. The command 3716 may comprise anindication of activation of the scheduling cell for the first cell. Thecommand 3716 may comprise a bit field indicating an activation ofcross-carrier scheduling for the first cell. The first cell may be aprimary cell of a cell group. The first cell may be a primary cell of aPUCCH group. The bit field may indicate the activation or a deactivationof cross-carrier scheduling of the primary cell of the cell group or theprimary cell of the PUCCH group. The wireless device 3708 may beconfigured with cross-carrier scheduling either for the primary cell ofthe cell group or the primary cell of the PUCCH group. The wirelessdevice 3708 may or may not expect to be configured with cross-carrierscheduling for both the primary cell of the cell group and the primarycell of the PUCCH group. The wireless device 3708 may ignore the command3716 (e.g. ignore the bit field and continue cross-carrier scheduling),for example, if the command 3716 indicates the activation ofcross-carrier scheduling for the first cell and if the first cell isalready activated with cross-carrier scheduling. The command 3716 mayactivate one or more secondary cells. The wireless device 3708 (e.g., ator after time T) may determine (e.g., step 3754) the scheduling cell.The wireless device 3708 may determine an indicator (e.g., index oridentifier) of the scheduling cell based on the one or more secondarycells activated by the command 3716, for example, based on the command3716 comprising an indication of activation of cross-carrier scheduling.The wireless device 3708 may select a secondary cell, among the one ormore secondary cells, with a lowest index among indices of the one ormore secondary cells as the scheduling cell. The wireless device 3708may activate cross-carrier scheduling based on determining thescheduling cell.

The wireless device 3708 may monitor a second search space (e.g., SS2)of the scheduling cell for second DCI (e.g., DCI-2 3718) comprisingresource assignments for the first cell. The base station 3704 may send(e.g., step 3736), via the second search space of the scheduling cell,the second DCI. As further described herein the second DCI may be basedon (e.g., scrambled with) a second RNTI. The wireless device 3708 mayreceive (e.g., step 3756), via the second search space of the schedulingcell, the second DCI. The second DCI may comprise resource assignmentsfor the first cell. The base station 3704 may send (e.g., step 3738),via the first cell and based on the assigned resources indicated by thesecond DCI, downlink data 3720. The wireless device may receive (e.g.,step 3758), via the first cell and based on the assigned resourcesindicated by the second DCI, the downlink data 3720.

FIG. 37D and FIG. 37E show an example method 3770 that may be performedby the base station 3704 and an example method 3784 that may beperformed by the wireless device 3708, respectively. Steps 3772-3782 ofFIG. 37D may be similar to steps 3734-3742, respectively, as describedwith reference to FIG. 37B. Steps 3786-3794 of FIG. 37E may be similarto steps 3754-3762, respectively, as described with reference to FIG.37C.

The command 3716 may comprise a bit field indicating the scheduling cellindicator (e.g, index or identifier) for cross-carrier scheduling of thefirst cell. The scheduling cell may be activated and the wireless device3708 may activate cross-carrier scheduling for the first cell. Thecommand 3716 may comprise a second scheduling cell indicator/index of asecond scheduling cell and a secondary cell indicator/index of a secondsecondary cell. The second secondary cell may be a scheduled cellassociated with the second scheduling cell, for example, based oncross-carrier scheduling being configured for the second secondary cell.

The wireless device 3708 may continue monitoring the first search spacefor the DCIs, regardless of whether or not cross-carrier scheduling isenabled. The base station 3704 may send (e.g., step 3740), via the firstsearch space (e.g., SS1) of the first cell, third DCI (e.g., DCI-33722). The third DCI may comprise resource assignments for data 3724 viathe first cell. The wireless device 3708 may receive (e.g., step 3760),via the first search space of the first cell, the third DCI. The basestation 3704 may send (e.g., step 3742), via the first cell and based onthe assigned resources indicated by the third DCI, the data 3724. Thewireless device 3708 may receive (e.g., step 3762), via the first celland based on the third DCI, the data 3724.

The first DCI may be based on fallback DCI formats. The first DCI may bebased on non-fallback DCI formats. The first DCI, sent via the firstsearch space of the first cell, may be scrambled with a first RNTI(e.g., RNTI 1). The second DCI (e.g., comprising resource assignmentsfor the first cell), sent via the second search space of the secondcell, may be scrambled with a second RNTI (e.g., RNTI 2). The first RNTImay be a C-RNTI (e.g., an RNTI used if the wireless device is in an RRCconnected state). The second RNTI may be configured for the first cell,by the base station, for supporting cross-carrier scheduling. A wirelessdevice may be associated with a plurality of cells configured withcross-carrier scheduling. A single RNTI may be shared among theplurality of cells or the base station may configure independent (e.g.,different) RNTIs for each scheduled cell, for example, if the wirelessdevice is associated with a plurality of cells configured withcross-carrier scheduling.

The wireless device 3708 may determine the scheduling cell based on thecommand 3716. The command 3716 may update the scheduling cell indicator,for example, if the one or more parameters for cross-carrier scheduling(e.g., cross-carrier configuration 3710) comprise the scheduling cellindicator. The one or more parameters may or may not comprise thescheduling cell indicator. The one or more parameters may indicate thatthe first cell is configured with cross-carrier scheduling. Otherparameters to support the cross-carrier scheduling (e.g., the schedulingcell indicator) may be available via separate RRC signaling, MAC CE(s)and/or DCI(s).

The wireless device 3708 may determine the second RNTI, used for thesecond DCI, based on the first RNTI. The wireless device 3708 maydetermine the second RNTI by adding a fixed value to the first RNTI. Thefirst RNTI may be an RNTI used for DCI comprising resource assignmentsfor wireless device-specific data (e.g., for a serving cell configuredfor the wireless device). The first RNTI may be a C-RNTI, a CS-RNTI, anSP CSI C-RNTI, or an MCS-C-RNTI. The second RNTI may be C-RNTI+v,CS-RNTI+v, SP CSI C-RNTI+v, or MCS-C-RNTI+v. The base station mayconfigure the value v via a RRC signaling. The value of v may be fixedor may be reconfigurable.

A base station may configure one or more RNTIs used for DCI, via one ormore search spaces of a second cell, comprising resource assignments fora first cell. A wireless device may monitor, based on the one or moreRNTIs, one or more search spaces of a second cell for the DCI. Thesecond cell may be a scheduling cell for the first cell. The basestation may configure a first RNTI (e.g., C-RNTI). The wireless maymonitor, based on the first RNTI, the one or more search spaces of thesecond cell for the DCI. The wireless device may not monitor the one ormore search spaces for second DCI that is not scrambled with a validRNTI (e.g., the first RNTI) or that is scrambled with a second RNTI thatis different from the first RNTI. The base station may have notconfigured the second RNTI, for the first cell, for DCIs monitored viathe one or more search spaces of the second cell. For example, thewireless device may not monitor the one or more search spaces for secondDCI comprising an activation/release of a downlink SPS configuration oran activation/release of uplink configured grant as the wireless deviceis not configured with a proper RNTI for the second cell. The wirelessdevice may monitor the one or more search spaces of the second cellbased on the one or more RNTIs, for example, if cross-carrier schedulingis activated. The one or more RNTIs may comprise the first RNTI and maynot comprise the second RNTI.

A base station may configure a first cell in a frequency spectrum. Thefrequency spectrum may be shared among multiple RATs and/or multiplebase stations. Control channel capacity of a first RAT may be affectedbased on utilization of the frequency spectrum by a second RAT.Fluctuating control channel capacity may lead to low quality of service((e.g., increased latency), for example, if the first cell is a primarycell for a wireless device. The base station may configure additionalsearch space in a second cell, where the wireless device may monitor theadditional search space if the first cell is not available for a searchspace. The additional search space may carry one or more DCIs comprisingresource assignments for the first cell. Utilizing the second cell mayaddress the control channel capacity of the first cell. Monitoring theadditional search space may only be performed if the wireless device maynot monitor the search space of the first cell. A wireless devicecapability (e.g., blind decoding candidates, number of non-overlappedCCEs) is not required to be increased with a time-domain partitioningbetween the first cell and the second cell for control channels. Thewireless device capability may be used for the first cell or the secondcell depending on the availability of the search space of the firstcell.

A base station may configure cross-carrier scheduling and self-carrierscheduling for a first cell for a wireless device. The base station mayconfigure, for the wireless device, a first search space of the firstcell for self-carrier scheduling. The base station may configure asecond search space of a second cell (e.g., a scheduling cell for thefirst cell) for the cross-carrier scheduling. The base station mayconfigure a first periodicity P1 (e.g., 1 slot, or any other quantity ofslots and/or time period) for the first search space. The base stationmay configure a second periodicity P2 (e.g., 2 slots, or any otherquantity of slots and/or time period) for the second search space. Thewireless device may monitor the first search space for a first DCI orthe second search space for a second DCI (e.g., performing witherself-carrier scheduling or cross-carrier scheduling) based on a slotformation indication for one or more slots for the first cell. Thewireless device may perform self-carrier scheduling, for example, if theslot formation indication for a first slot, among the one or more slots,indicates a downlink slot that is available for downlink reception(e.g., control monitoring occasion of the first search space is valid).The wireless device may monitor the first search space for the first DCIbased on self-carrier scheduling. The wireless device may not be able toreceive any DCI via the first search space, for example, if the slotformation indication for the first slot, among the one or more slots,indicates an unavailable slot (e.g., no downlink reception or uplinktransmission). The wireless device may apply cross-carrier schedulingand monitor the second search space for the second DCI, for example, ifthe slot formation indication for the first slot, among the one or moreslots, indicates an unavailable slot.

The wireless device may perform either the self-carrier scheduling orthe cross-carrier scheduling in a slot of the first cell. The wirelessdevice may determine to perform self-carrier scheduling for a slot, forexample, if at least one search space monitoring occasion of a searchspace in the slot is configured for valid downlink symbols (e.g., OFDMsymbols) by the slot formation indication of the slot. The wirelessdevice may determine to perform cross-carrier scheduling for the slot,for example, if no search space monitoring occasion of a search space inthe slot is available for valid downlink symbols. The wireless devicemay monitor the second search space of the second cell for the secondDCI if cross-carrier scheduling is used. The wireless device maydetermine whether to perform self-carrier scheduling or cross-carrierscheduling based on a slot of the second cell, for example, if asubcarrier spacing of the second cell is higher than a subcarrierspacing of the first cell. The wireless device may determine, for a slotof the second cell, whether to perform self-carrier scheduling orcross-carrier scheduling, for example, based on whether or not there isa valid search space monitoring occasion of any search space configuredfor the first cell within the slot. The wireless device may determinewhether to perform self-carrier scheduling or cross-carrier schedulingin a slot of the first cell, for example, if the subcarrier spacing ofthe second cell is equal to or smaller than the first cell. The wirelessdevice may determine whether to perform self-carrier scheduling orcross-carrier scheduling for a span of the first cell. A span maycomprise one or more consecutive symbols comprising one or more searchspace monitoring occasions in a slot of the first cell. The wirelessdevice may determine whether to use self-carrier scheduling orcross-carrier scheduling for a span of the second cell, for example, atleast if the subcarrier spacing of the second cell is larger than thesubcarrier spacing of the first cell.

FIG. 38A shows an example of self-carrier scheduling and cross-carrierscheduling. A wireless device 3808 may perform self-carrier schedulingor cross-carrier scheduling within a time interval (e.g., a slot) basedon whether a monitoring occasion of a search space of a cell isconfigured on valid downlink symbols. FIG. 38B and FIG. 38C show examplemethods at a base station 3804 and the wireless device 3808,respectively, for cross-carrier and self-carrier scheduling.

The base station 3804 may send (e.g., step 3832), to the wireless device3808, one or more parameters for cross-carrier scheduling (e.g.,cross-carrier configuration 3810) of a first cell (e.g., primary cell,cell 0). The wireless device 3808 may receive (e.g., step 3852) the oneor more configuration parameters. A second cell (e.g., a secondary cell,cell 1) may be indicated (e.g., via the one or more parameters) as ascheduling cell for the first cell. The base station 3804 may configurethe wireless device with (e.g., indicate to the wireless device 3808) afirst search space (e.g., SS1) of the first cell. The base station 3804may configure the wireless device with (e.g., indicate to the wirelessdevice 3808) a second search space (e.g., SS2) of the second cell forcross-carrier scheduling of the first cell. The base station 3804 mayindicate a monitoring periodicity of the first search space (e.g., P1)and a monitoring periodicity of the second search space. A monitoringperiodicity of the first search space may be one slot (e.g., or anyother quantity of slots) based on a numerology of the first cell. Amonitoring periodicity of the second search space may be two slots(e.g., or any other quantity of slots) based on a numerology of thesecond cell that may be the same as the numerology of the first cell.The base station 3804 may send, to the wireless device 3808, a firstslot format indicator/indication for the first cell and a second slotformat indicator/indication for the second cell. The first slot formatindicator may indicate whether symbols in a slot are valid fortransmissions (e.g., downlink transmission) or are unavailable. Thefirst slot format indication for the first cell may indicate downlinktransmission for a slot n, downlink transmission for a first portion ofslot n+1 and non-availability for a second portion of slot n+1,non-availability for a first portion of slot n+2 and downlinktransmission for a second portion of slot n+2, and downlink transmissionfor slot n+3. The second slot format indication for the second cell mayindicate downlink transmission for slots n, n+1, n+2, and n+3.

The wireless device 3808 may perform, for the first cell, self-carrierscheduling or cross-carrier scheduling in a slot based on determiningwhether a search space monitoring occasion for the first search space inthe slot is configured on valid downlink symbols. The wireless devicemay determine whether the search space monitoring occasion for the firstsearch space in the slot is configured on valid downlink symbols basedon the first slot format indication of the first cell.

The wireless device 3808 may have a valid monitoring occasion, in theslot n, for the first search space. The base station 3804 and/or thewireless device 3808 may determine to perform self-carrier scheduling inslot n (e.g., steps 3838, 3858), for example, based on the wirelessdevice 3808 having a monitoring occasion, for the first search space inslot n, on valid downlink OFDM symbols. The base station 3804 may send(e.g., step 3840), to the wireless device 3808 via the first searchspace, first DCI (e.g., DCI-1 3812). The first DCI may comprise resourceassignments for the first cell. The wireless device 3808 may receive(e.g., step 3860), via the first search space, the first DCI. The basestation 3804 may send (e.g., step 3842) and the wireless device 3808 mayreceive (e.g., step 3862), via the first cell, downlink datacorresponding to the first DCI. The base station 3804 and/or thewireless device 3808 may similarly perform the self-carrier schedulingin slot n+1 based on a monitoring occasion of the slot n+1 beingconfigured on valid downlink OFDM symbols.

The base station 3804 and/or the wireless device 3808 may determine toperform cross-carrier scheduling in slot n+2 (e.g., steps 3834, 3854),for example, based on the wireless device 3808 not having a monitoringoccasion, for the first search space in slot n+2, on valid downlink OFDMsymbols. The wireless device 3808 may monitor the second search spacefor second DCI (e.g., DCI-2 3816). The base station 3804 may send (e.g.,step 3836), to the wireless device 3808 via the second search space,second DCI (e.g., DCI-2 3816). The second DCI may comprise resourceassignments for the first cell. The wireless device 3808 may receive(e.g., step 3856), via the second search space, the second DCI. The basestation 3804 may send (e.g., step 3842) and the wireless device 3808 mayreceive (e.g., step 3862), via the first cell, downlink datacorresponding to the second DCI.

The base station 3804 and/or wireless device 3808 may determine toperform self-carrier scheduling (e.g., steps 3838, 3858) in slot n+3based on the monitoring occasion of the first search space in slot n+3being configured on valid downlink OFDM symbols. The base station 3804may send (e.g., step 3840), to the wireless device 3808 via the firstsearch space, third DCI (e.g., DCI-3 3820). The third DCI may compriseresource assignments for the first cell. The wireless device 3808 mayreceive (e.g., step 3860), via the first search space, the third DCI(DCI-3) scheduling data for the first cell. The base station 3804 maysend (e.g., step 3842) and the wireless device 3808 may receive (e.g.,step 3862), via the first cell, downlink data corresponding to the thirdDCI.

FIG. 38D and FIG. 38E show an example method 3870 that may be performedby the base station 3804 and an example method 3884 that may beperformed by the wireless device 3808, respectively. Steps 3874-3882 ofFIG. 38D may be similar to steps 3834-3842, respectively, as describedwith reference to FIG. 38B. Steps 3886-3894 of FIG. 38E may be similarto steps 3854-3862, respectively, as described with reference to FIG.38C.

Wireless device complexity relating to a quantity of blind decodingcandidates per slot may be maintained and need not be increased byperforming self-carrier scheduling or a cross-carrier scheduling at agiven slot. The wireless device may be able to receive, for the firstcell, DCI from either the first cell or the second cell depending on theavailability of the first cell. Various examples herein enable increasedcontrol channel capacity for the first cell (e.g., a primary cell of acell group) without increasing wireless device complexity.

A wireless device may receive one or more configuration messages (e.g.,RRC messages). The one or more configuration messages may compriseconfiguration parameters for a first cell. The configuration parametersmay comprise an indication of cross-carrier scheduling and one or moremonitoring occasions of a first search space of the first cell. Theconfiguration parameters may indicate a second search space of a secondcell used for cross-carrier scheduling of the first cell. The secondcell may be a scheduling cell for the first cell. The wireless devicemay receive a slot format indication-DCI (e.g., SFI-DCI) comprising aslot format indication of one or more slots of the first cell. Thewireless device may determine, based on the SFI-DCI, that a firstmonitoring occasion, of the one or more monitoring occasions of thefirst search space, fully overlaps with one or more downlink OFDMsymbols of a first slot of the first cell. The wireless device maymonitor the first monitoring occasion in the first slot for a first DCI,for example, based on the determining that the first monitoring occasionfully overlaps with the one or more downlink OFDM symbols of the firstslot. The first DCI may comprise resource assignments for the firstcell. The wireless device may that determine a second monitoringoccasion, of the one or more monitoring occasions of the first searchspace, may not fully overlap with one or more downlink OFDM symbols in asecond slot of the first cell. The wireless device may determine thatthe second monitoring occasion is invalid based on the second monitoringoccasion not fully overlapping with one or more downlink OFDM symbols inthe second slot of the first cell The wireless device may monitor thesecond search space in the second slot for a second DCI, for example,based on determining that the second monitoring occasion is invalid. Thesecond DCI may comprise resource assignments for the first cell.

The wireless device may or may not monitor the first search space in thesecond slot and may monitor the second search space in the second slotbased on the cross-carrier scheduling. The wireless device may or maynot monitor the second search space in the first slot and may monitorthe first search space on the first slot base on the self-carrierscheduling.

A wireless device may receive one or more configuration messages. Theone or more configuration messages may comprise configuration parametersfor a first cell. The configuration parameters may comprise anindication of cross-carrier scheduling, one or more first DCI formatsfor self-carrier scheduling, and one or more second DCI formats for thecross-carrier scheduling. The configuration parameters may indicate oneor more first search spaces for monitoring for first DCIs comprisingresource assignments for the first cell. The wireless device may receivea command indicating a second cell as a scheduling cell forcross-carrier scheduling of the first cell. The wireless device maydetermine one or more second search spaces of the second cell based onone or more second DCI formats for the cross-carrier scheduling. Thewireless device may monitor the one or more first search spaces of thefirst cell for the first DCIs based on the one or more first DCIformats. The first DCIs may comprise resource assignments for the firstcell. The wireless device may monitor the one or more second searchspaces of the second cell for second DCIs based on one or more secondDCI formats. The second DCIs may comprise resource assignments for thefirst cell.

The wireless device may monitor the one or more second search spaces ofthe second cell for the second DCIs based on a second RNTI. The wirelessdevice may monitor the one or more first search spaces of the first cellfor the first DCIs based on a first RNI. The wireless device maydetermine a second DCI size of the one or more second DCI formats basedon an active DL and/or UL BWPs of the second cell. The wireless devicemay align a first DCI size, of the one or more second DCI formats, tothe second DCI size based an active DL and/or UL BWPs of the first cell.The one or more first search spaces may be cell-specific search spaces(e.g., common search spaces) and/or wireless device-specific searchspaces. The one or more first DCI formats may comprise fallback DCIformats ((e.g., DCI format 1_0 and DCI format 0_0). The one or moresecond search spaces may be wireless device-specific search spaces. Theone or more second DCI formats may comprise non-fallback DCI formats(e.g., DCI format 1_1 and DCI format 0_1). The one or more first DCIformats may comprise the DCI format 1_0/0_0 and DCI format 1_1/0_1. Theone or more second DCI formats may comprise the DCI format 1_1/0_1. Thewireless device may determine the one or more second search spaces ofthe second cell among one or more third search spaces of an active DLBWP of the second cell. The wireless device may be configured to monitorthe one or more second search spaces and/or the one or more third searchspaces for DCIs based on the second DCI formats (e.g., DCI format1_1/0_1). The wireless device may monitor the one or more first searchspaces of the first cell and the one or more second search spaces of thesecond cell for DCIs based on the second DCI formats. The DCIs maycomprise resource assignments for the first cell.

FIG. 39A shows an example of switching between self-carrier schedulingand cross-carrier scheduling for a cell. A base station 3904 mayactivate cross-carrier scheduling for a cell. Different formats (e.g.,DCI formats) may be used to differentiate between control signals (e.g.,DCIs) associated with cross-carrier scheduling and self-carrierscheduling. FIG. 37B and FIG. 37C show example methods at the basestation 3704 and the wireless device 3708, respectively, forcross-carrier and self-carrier scheduling. The base station 3904 and thewireless device 3908 may perform one or more operations described withreference to the base station 3704 and the wireless device 3708 asdescribed with reference to FIGS. 37A-C.

The base station 3904 may send (e.g., step 3932) one or moreconfiguration parameters (e.g., via RRC signaling) for cross-carrierscheduling (e.g., cross-carrier configuration 3910) for a first cell.The wireless device 3908 may receive (e.g., step 3952) the one or moreconfiguration parameters. The one or more configuration parameters maycomprise a scheduling cell indicator/index (e.g., of a scheduling cell)and a second DCI format for DCIs to be monitored on the scheduling cellfor the first cell if cross-carrier scheduling is enabled. The wirelessdevice 3908 may be configured with a first search space (e.g., SS1) ofthe first cell for self-carrier scheduling. The wireless device 3908 maymonitor the first search space for DCIs based on a first DCI format(e.g., DCI format 1) via. The wireless device 3908 may monitor a secondsearch space (e.g., SS2) of the scheduling cell for second DCI based onthe second DCI format, for example, based on an activation ofcross-carrier scheduling for the first cell. The wireless device 3908may continue to monitor the first search space of the first cell forDCIs based on the first DCI format, for example, based on the activationof cross-carrier scheduling for the first cell. The first DCI format maybe the same as the second DCI format. The first DCI format may comprisethe second DCI format. The first DCI format may be a fallback DCI formatfor downlink and/or uplink data scheduling (e.g., DCI format 0_0/1_0).The second DCI format may be non-fallback DCI formats (e.g., DCI format1_1/0_1).

The wireless device 3908 may operate using self-carrier scheduling forthe first cell, for example, until the wireless device 3908 receives acommand to activate cross-carrier scheduling for the first cell. Thebase station 3904 may send (e.g., step 3940), via the first search spaceof the first cell, first DCI (e.g., DCI-1 3912). The first DCI maycorrespond to the first DCI format. The first DCI may comprise resourceassignments for downlink data 3914 for the first cell. The wirelessdevice 3908 may receive (e.g., step 3960), via the first search space ofthe first cell, the first DCI. The base station 3904 may send (e.g.,step 3942), via the first cell and based on the assigned resourcesindicated by the first DCI, the downlink data 3914. The wireless device3908 may receive (e.g., step 3962), via the first cell and based on theassigned resources indicated by the first DCI, the data 3914.

The base station 3904 may send (e.g., step 3934), to the wireless device3908, a command 3916 to activate cross-carrier scheduling for the firstcell. The command may be a MAC CE or DCI. The wireless device 3908 maymonitor the second search space of the scheduling cell for second DCI(e.g., DCI-2 3918) comprising resource assignments for the first cell.The base station 3904 may send (e.g., step 3936), via the second searchspace of the scheduling cell, the second DCI. The second DCI maycorrespond to the second DCI format. The wireless device 3908 mayreceive (e.g., step 3956), via the second search space of the schedulingcell, the second DCI. The second DCI may comprise resource assignmentsfor the first cell. The base station 3904 may send (e.g., step 3938),via the first cell and based on the assigned resources indicated by thesecond DCI, downlink data 3920. The wireless device 3908 may receive(e.g., step 3958), via the first cell and based on the assignedresources indicated by the second DCI, the downlink data 3920.

The wireless device 3908 may continue monitoring the first search spacefor DCIs, regardless of whether or not cross-carrier scheduling isenabled. The base station 3904 may send (e.g., step 3940), via the firstsearch space (e.g., SS1) of the first cell, third DCI (e.g., DCI-33922). The third DCI may comprise resource assignments for data 3924 viathe first cell. The wireless device 3908 may receive (e.g., step 3960),via the first search space of the first cell, the third DCI. The basestation 3904 may send (e.g., step 3942), via the first cell and based onthe assigned resources indicated by the third DCI, the data 3924. Thewireless device 3908 may receive (e.g., step 3962), via the first celland based on the third DCI, the data 3924.

FIG. 39D and FIG. 39E show an example method 3970 that may be performedby the base station 3904 and an example method 3984 that may beperformed by the wireless device 3908, respectively. Steps 3974-3982 ofFIG. 39D may be similar to steps 3934-3942, respectively, as describedwith reference to FIG. 39B. Steps 3986-3994 of FIG. 39E may be similarto steps 3954-3962, respectively, as described with reference to FIG.39C.

Various examples described herein (e.g., with reference to FIGS. 37-39 )may be applied for scheduling downlink transmissions or uplinktransmissions. With reference to FIG. 37A, for example, the DCIs (e.g.,DCI-1 3712, DCI-2 3718, or DCI-3 3712) may schedule resources for eithera downlink transmission or an uplink transmission.

A base station may send/transmit one or more configuration messages(e.g., RRC messages). The one or more configuration messages maycomprise one or more parameters for cross-carrier scheduling for a cell.The base station may send/configure a cross-carrier schedulingconfiguration (e.g., CrossCarrierSchedulingConfig) as a part of one ormore parameters configured for the cell (e.g., ServingCellConfig). Thecross-carrier scheduling configuration may comprise an indicator (e.g.,cif-Presence) for a second cell. The indicator may indicate whether acarrier indicator field is present in DCI (e.g., from the second cell).The second cell may be a scheduling cell for the cell. The cross-carrierscheduling configuration may comprise one or more additional parameters(e.g., schedulingCellId and cif-InSchedulingCell) for the cell. Theparameter schedulingCellId may comprise an indicator/index (e.g.,servngcellindex) corresponding to the second cell. The parametercif-InSchedulingCell may indicate an indicator/index for the cell byDCI, via the second cell, scheduling the cell.

The cross-carrier scheduling configuration may be configured for thecell. The cell may be a primary cell of the cell group or the PUCCHSCell. The wireless device may or may not activate the one or moreparameters of the cross-carrier scheduling configuration (e.g., activatethe cross-carrier scheduling), for example, based on/in response to thereceiving the cross-carrier scheduling configuration for the cell. Thebase station may indicate, to the wireless device, activation of thecross-carrier scheduling configuration for the cell via MAC CEs (e.g.,SCell activation MAC CE, comprising an enable/disable indication),and/or DCIs (e.g., comprising an enable/disable indication), forexample, after the cross-carrier scheduling configuration is configuredfor the cell.

FIG. 40 shows an example cross-carrier scheduling configuration (e.g.,as indicated to a wireless device). The cross-carrier schedulingconfiguration may comprise an indicator/index of a scheduled cell (e.g.,scheduledCellId). The cross-carrier scheduling configuration may beconfigured for a scheduling cell that schedules transmissions via thescheduled cell.

A base station may configure (e.g., indicate to a wireless device) oneor more parameters for cross-carrier scheduling for a first cell. Thewireless device may not activate cross-carrier scheduling for the firstcell until the wireless device may receive a command from the basestation. The base station may send/transmit a command (e.g., an SCellactivation/deactivation MAC CE). The MAC CE may comprise an indicationfor enabling or disabling the cross-carrier scheduling of the firstcell. A first MAC CE may comprise one or more indications to activateand/or deactivate one or more secondary cells of a cell group. The firstMAC CE may enable or disable the cross-carrier scheduling of a primarycell (e.g., the first cell) of the cell group, for example, if the cellgroup comprises the primary cell without an additional PUCCH cell. Thefirst MAC CE may enable or disable cross-carrier scheduling of theprimary cell of the cell group, for example, the cell group comprisesthe primary cell (e.g., the first cell) and a PUCCH cell. Cross-carrierscheduling may be activated by RRC configuration (e.g., withoutreceiving an additional MAC CE indication), for example, if thecross-carrier scheduling is configured for the PUCCH cell. A MAC CE mayenable r disable cross-carrier scheduling of the primary cell and thePUCCH cell, for example, if cross-carrier scheduling is configured forboth the primary cell and the PUCCH cell. The first MAC CE may notenable or disable cross-carrier scheduling, for example, ifcross-carrier scheduling is not configured for the primary cell.Enabling or disabling cross-carrier scheduling may be indicated via areserved bit in the MAC CE (e.g., SCell activation/deactivation MAC CE).

FIGS. 41A and 41B shows example MAC CE formats. The MAC CE formats maycorrespond to an SCell activation/deactivation MAC CE. FIG. 41A shows anexample of an SCell activation/deactivation MAC CE 4105 comprising oneoctet. FIG. 41B shows an example of an SCell Activation/Deactivation MACCE 4110 comprising four octets. MAC CEs 4105 and 4110 may be similar tothe MAC CEs described with reference to FIGS. 17A and 17B.

The example MAC CE formats may correspond to MAC CEs for enabling ordisabling cross-carrier scheduling for a primary cell of a cell group. Areserved bit field (e.g., bit E in FIGS. 41A and 41B) of the SCellactivation/deactivation MAC CE may be used to indicate enabling ordisabling of cross-carrier scheduling for a primary cell of a cell groupor a primary cell of a PUCCH group. The wireless device may or may notexpect to be configured with cross-carrier scheduling for both theprimary cell of the cell group and a PUCCH cell belonging to the samecell group.

A base station may configure cross-carrier scheduling for a first cellvia one or more configuration messages (e.g., RRC signaling). The RRCsignaling may or may not configure/indicate a scheduling cellindicator/index. The base station may update or configure the schedulingcell indicator/index via MAC CEs and/or DCI signaling. The base stationmay indicate, via a first MAC CE, a scheduling cell indicator/index forthe first cell. The first cell may be a primary cell of a cell groupcomprising the first cell and the scheduling cell. The first MAC CE(e.g., an SCell activation/deactivation MAC CE) may comprise one or moreentries for activation/deactivation for one or more secondary cells ofthe cell group. The first MAC CE may comprise the scheduling cellindicator/index of a scheduling cell for the first cell. The wirelessdevice may apply the indicated scheduling cell for the first cell andmay activate cross-carrier scheduling for the first cell, for example,based on receiving the scheduling cell indicator/index. The schedulingindicator/index may be 3 bits (e.g., to indicate a value in a range of 0to 7 or 1 to 8), for example, if the MAC CE may correspond to up to 7 or8 secondary cells. The scheduling cell index may be 5 bits (e.g., toindicate a value in a range of 0 to 31 or 1 to 32), for example, if theMAC CE correspond to up to 31 or 32 secondary cells. The scheduling cellindicator/index may be fixed as K bits (e.g., 3 bits, or any otherquantity of bits) and a value of the scheduling cell indicator/index mayrange from indicator/index 0 (e.g., corresponding to a first SCell) toindicator/index 2^(K)−1 (e.g., corresponding to an eighth SCell). Ascheduling cell of a primary cell of a cell group may bedetermined/updated based on a MAC CE (e.g., SCellactivation/deactivation MAC CE). A scheduling cell for a secondary cellof the cell group may be determined based on RRC configurations (e.g.,CrossCarrierSchedulingConfig of the secondary cell may compriseschedulingCellId).

FIGS. 42A and 42B show example MAC CE formats. The MAC CE formats maycorrespond to SCell activation/deactivation MAC CEs. A MAC CE 4205 maybe used for activation/deactivation of 7 secondary cells (e.g., via bitsC1 to C7). A MAC CE 4210 may be used for activation/deactivation of 31secondary cells. The MAC CEs 4205 and 4210 may indicate a schedulingcell for cross-carrier scheduling for a primary cell of a cell group.MAC CEs 4105 and 4110 may be similar to the MAC CEs described withreference to FIGS. 17A and 17B except for additional bits that may addedto indicate the scheduling cell.

An octet comprising a cell indicator/index (e.g., a scheduling cellindicator/index) and one or more reserved bits may be added to an SCellactivation/deactivation MAC CE. The octet comprising the cellindicator/index and the one or more reserved bits may be formed as adedicated MAC CE that may be separate from the SCellactivation/deactivation MAC CE.

A base station may send/transmit a MAC CE to activate and/or deactivatecross-carrier scheduling for a first cell. The MAC CE may comprise oneor more entries to activate and/or deactivate cross-carrier schedulingfor one or more cells. An entry of the MAC CE may comprise a scheduledcell indicator/index of a scheduled cell. The entry of the MAC CE maycomprise a scheduling cell indicator/index, of a scheduling cell,corresponding to the scheduled cell indicator/index. The entry of theMAC CE may comprise a CIF value used for cross-carrier scheduling. Thewireless device may determine/assume that cross-carrier scheduling isenabled, for example, if the scheduled cell indicator/index and thescheduling cell indicator/index are different. The wireless device maydetermine/assume that self-carrier scheduling is enabled (e.g., orcross-carrier scheduling is disabled), for example, if the scheduledcell indicator/index and the scheduling cell indicator/are same.

A base station may configure a scheduling cell indicator/index for ascheduled cell, for example, via RRC signaling. The base station mayindicate/configure cross-carrier scheduling configuration (e.g.,CrossCarrierSchedulingConfig) for the scheduled cell and/or thescheduling cell. The base station may activate or deactivatecross-carrier scheduling for each scheduled cell (e.g., via MAC CEsand/or DCIs). The base station may configure a plurality of cells of acell group for a wireless device. The base station may configure a firstcell of the plurality of cells for cross-carrier scheduling (e.g., viaCrossCarrierSchedulingConfig). The base station may configure a secondcell of the plurality of cells for cross-carrier scheduling (e.g., viaCrossCarrierSchedulingConfig). A cell indicator/index of the first cellmay M and a cell indicator/index of the second cell may be K (e.g., Mand K>1). The base station may send, to the wireless device, a use MACCE for enabling/disabling cross-carrier scheduling for the first celland the second cell of the cell group. The base station may use two bitsof the MAC CE for enabling disabling cross-carrier scheduling for thefirst cell and the second cell. The first bit may correspond to thefirst cell, for example, if the cell indicator/index of the first cellis smaller than the cell indicator/index of the second cell. The secondbit may correspond to the second cell. A quantity of bits of the MAC CEto be used for enabling or disabling cross-carrier scheduling may bedetermined based on a quantity of cells configured with cross-carrierscheduling. A quantity of bits of the MAC CE may be determined based ona quantity of configured secondary cells (e.g., 8 bits if a quantity ofconfigured secondary cells is less than 8 and 32 bits if the quantity isgreater than 8, or any other quantity of bits).

A MAC CE may comprise P bits indicating a scheduling cellindicator/index and S bits for indicating enabling/disablingcross-carrier scheduling (e.g., for S secondary cells). The schedulingcell indicator/index may indicate scheduling cell for a primary cell ofa cell group, for example, if the MAC CE is sent/transmitted for thecell group. Each bit of S bits may indicate whether to enable or disablecross-carrier scheduling for a corresponding secondary cell of the cellgroup. S may be determined based on a quantity of secondary cellsconfigured with cross-carrier scheduling. S may be determined based on aquantity of configured secondary cells.

FIG. 43A shows an example method for monitoring search spaces based onRNTIs. The example method 4300 may be performed at a wireless device. Atstep 4304, the wireless device may receive a cross-carrier schedulingconfiguration for a cell. The cross-carrier scheduling configuration maycomprise an indicator of a scheduling cell for the cell. At step 4308,the wireless device may receive a first search space configuration. Thefirst search space configuration may be associated with a first searchspace of the cell configured for self-carrier scheduling. The firstsearch space configuration may comprise an indicator of the first searchspace. The first search space configuration may comprise a first RNTIassociated with self-carrier scheduling. At step 4312, the wirelessdevice may receive a second search space configuration. The secondsearch space configuration may be associated with a second search spaceof the scheduling cell. The second search space configuration maycomprise an indicator of the second search space. The second searchspace configuration may comprise a second RNTI associated withcross-carrier scheduling.

At step 4316, the wireless device may determine whether cross-carrierscheduling is enabled/activated for the cell. The wireless device maydetermine that cross-carrier scheduling is enabled based on receiving anindication. The indication may be DCI, a MAC CE, or an RRC configurationmessage. The indication may be a command activating the scheduling cell.

At step 4320, the wireless device may monitor the first search space ofthe cell based on first RNTI, for example, based on determining thatcross-carrier scheduling is not enabled. The wireless device may monitorthe first search space for receiving DCI scheduling transmission via thecell.

At step 4324, the wireless device may monitor the first search space ofthe cell based on first RNTI, for example, based on determining thatcross-carrier scheduling is enabled. The wireless device may monitor thefirst search space for receiving DCI scheduling transmission via thecell. The wireless device may additionally monitor the second searchspace of the scheduling cell based on the second RNTI, for example,based on determining that cross-carrier scheduling is enabled. Thewireless device may monitor the second search space for receiving DCIscheduling transmission via the cell.

FIG. 43B shows an example method for monitoring search spaces based onRNTIs. The example method 4450 may be performed by a wireless device.Steps 4358-4374 of FIG. 43B may be similar to steps 4308-4324,respectively, as described with reference to FIG. 43A.

FIG. 44A shows an example method for monitoring search spaces based on aslot format indication. The example method 4400 may be performed at awireless device. At step 4404, the wireless device may receive across-carrier scheduling configuration for a cell. The cross-carrierscheduling configuration may comprise an indicator of a scheduling cellfor the cell.

At step 4408, the wireless device may receive a first search spaceconfiguration. The first search space configuration may be associatedwith a first search space of the cell configured for self-carrierscheduling. The first search space configuration may comprise anindicator of the first search space. At step 4412, the wireless devicemay receive a second search space configuration. The second search spaceconfiguration may be associated with a second search space of thescheduling cell. The second search space configuration may comprise anindicator of the second search space. At step 4416, the wireless devicemay receive a slot format indication (e.g., via DCI). The slot formatindication may indicate whether symbols (e.g., OFDM symbols) in a slotare valid for transmissions (e.g., downlink transmission) or areunavailable. For example, the slot format indication may indicatedownlink OFDM symbols in a slot.

At step 4420, the wireless device may determine, for a slot of the cell,whether a monitoring occasion of the first search space is configured ondownlink OFDM symbols of the slot. At step 4424, the wireless device maymonitor the first search space in the slot, for example, based ondetermining that the monitoring occasion of the first search space, inthe slot, is configured on downlink OFDM symbols. The wireless devicemay monitor the first search space for receiving DCI schedulingtransmission via the cell.

At step 4428, the wireless device may monitor the second search space inthe slot, for example, based on determining that the monitoring occasionof the first search space, in the slot, is not configured on downlinkOFDM symbols. The wireless device may monitor the second search space ofthe scheduling cell for receiving DCI scheduling transmission via thecell.

FIG. 44B shows an example method for monitoring search spaces based on aslot format indication. The example method 4450 may be performed by awireless device. Steps 4454-4464 of FIG. 44B may be similar to steps4416-4428, respectively, as described with reference to FIG. 44A.

A wireless device may receive one or more RRC messages. The one or moreRRC messages may comprise configuration parameters. The configurationparameters may comprise an indication of cross-carrier scheduling for afirst cell, an indication of a first search space of the first cell, andan indication of a second search space of a second cell. The second cellmay be a scheduling cell for the first cell if cross-carrier schedulingis used for the first cell. The wireless device may determine acondition associated with a slot of the first cell. The condition may bethat there is no valid monitoring occasion of the first search space inthe slot of the first cell. The wireless device may stop monitoring thefirst search space of the first cell during the slot, for example, basedon determining that there is no valid monitoring occasion of the firstsearch space in the slot of the first cell. The wireless device maymonitor the second search space of the second cell in the slot forreceiving second DCI. The second DCI may comprise resource assignmentsfor the first cell.

A wireless device may receive one or more RRC messages. The one or moreRRC messages may comprise configuration parameters for cross-carrierscheduling for a first cell. The wireless device may receive a commandindicating that a second cell is a scheduling cell for the first cell.The command may be a MAC CE comprising a cell indicator/index of thescheduling cell. The command may be an SCell activation/deactivation MACCE comprising an indication (e.g., a bit) to enable or disablecross-carrier scheduling for the first cell. The wireless device mayreceive, via the second cell, DCI comprising a resource assignment forthe first cell. The wireless device may communicate with a base station,via the first cell, based on the resource assignment.

A wireless device may receive one or more RRC messages. The one or moreRRC messages may comprise configuration parameters for a first cell. Theconfiguration parameters may comprise indications of cross-carrierscheduling for the first cell, one or more first DCI formats forself-carrier scheduling, one or more second DCI formats forcross-carrier scheduling, and one or more first search spaces formonitoring for first DCIs comprising resource assignments for the firstcell. The wireless device may receive a command indicating that a secondcell is a scheduling cell for the first cell. The wireless device maydetermine one or more second search spaces of the second cell based onthe one or more second DCI formats for cross-carrier scheduling. Thewireless device may monitor the one or more first search spaces of thefirst cell for the first DCIs, for example, based on the one or morefirst DCI formats. The first DCIs may comprise resource assignments forthe first cell, via. The wireless device may monitor the one or moresecond search spaces of the second cell for second DCIs, for example,based on the one or more second DCI formats. The second DCIs maycomprise resource assignments for the first cell. The wireless devicemay monitor for the first DCIs based on a first RNTI. The wirelessdevice may monitor for the second DCIs based on a second RNTI.

A wireless device may receive one or more RRC messages. The one or moreRRC messages may comprise configuration parameters for a first cell. Theconfiguration parameters may comprise indications of cross-carrierscheduling, one or more monitoring occasions of a first search space ofa first cell, and a second search space of a second cell used forcross-carrier scheduling of the first cell. The second cell may be ascheduling cell for the first cell. The wireless device may receive aslot format indication DCI (e.g., SFI-DCI) comprising a slot formationindication of one or more slots of the first cell. The wireless devicemay determine that a first monitoring occasion, of the one or moremonitoring occasions of the first search space, overlaps fully with oneor more downlink OFDM symbols of a first slot of the first cell, forexample, based on the SFI-DCI. The wireless device may monitor the firstmonitoring occasion in the first slot for first DCI, for example, basedon determining that the first monitoring occasion overlaps fully withone or more downlink OFDM symbols of the first slot. The first DCI maycomprise resource assignments for the first cell. The wireless devicemay determine that a second monitoring occasion of the one or moremonitoring occasions of the first search space does not fully overlapwith one or more downlink OFDM symbols in a second slot of the firstcell. The wireless device may monitor the second search space of thesecond cell in the second slot for second DCI, for example, based ondetermining that the second monitoring occasion does not overlap fullywith one or more downlink OFDM symbols of the second slot. The secondDCI may comprise resource assignments for the first cell via.

A wireless device may perform a method comprising multiple operations.The wireless device may receive one or more messages comprisingconfiguration parameters for a primary cell, wherein the primary cellmay comprise a first search space and a second search space. Theconfiguration parameters may comprise: a first indication indicatingthat the first search space is enabled with self-carrier scheduling; anda second indication indicating that the second search space is enabledwith cross-carrier scheduling; and a third indication, of a secondarycell, for cross-carrier scheduling the primary cell. The wireless devicemay monitor for downlink control information (DCI), wherein themonitoring may comprise at least one of: monitoring, based on the firstindication, the first search space for self-carrier scheduling via theprimary cell; or monitoring, based on the second indication, a thirdsearch space for cross-carrier scheduling via the secondary cell. Thewireless device may receive, based on the monitoring for DCI, at leastone resource assignment for the primary cell. The wireless device mayalso perform one or more additional operations. The wireless device mayreceive a command indicating activation of cross-carrier scheduling forthe primary cell, wherein the monitoring the third search space may bebased on the activation of cross-carrier scheduling for the primarycell. The wireless device may determine, based on the second searchspace of the primary cell, the third search space of the secondary cell.The wireless device may receive, via the primary cell and based on theat least one resource assignment, downlink data. The receiving the atleast one resource assignment may comprise receiving the at least oneresource assignment via the third search space. The receiving the atleast one resource assignment may comprise receiving the at least oneresource assignment via the first search space. The wireless device maydetermine, based on the second search space of the primary cell, thethird search space of the secondary cell. The determining the thirdsearch space may comprise determining a search space indicator of thethird search space that is associated with a search space indicator ofthe second search space. The determining the third search space maycomprise determining the third search space based on a search spaceindicator of the third search space that is the same as a search spaceindicator of the second search space. The determining the third searchspace of the secondary cell may comprise determining the third searchspace based on a search space indicator of the third search space beinga sum of a search space indicator of the second search space and anoffset value. The determining the third search space of the secondarycell may comprise determining the third search space based on an orderof the second search space among one or more search spaces, of theprimary cell, enabled with cross-carrier scheduling. The configurationparameters may indicate a quantity of control channel candidates for thesecond search space, wherein the monitoring the third search space ofthe secondary cell may comprise monitoring the third search space basedon the quantity of control channels for the second search space. Theconfiguration parameters may indicate that the first search space isconfigured with self-carrier scheduling and an indication ofcross-carrier scheduling may be absent for the first search space. Asearch space indicator of the second search space may be greater than asearch space indicator of the first search space. The configurationparameters may comprise a parameter indicating disabling cross-carrierscheduling for the first search space. The wireless device may determinethat the first search space is for self-carrier scheduling based on theparameter indicating disabling of cross-carrier scheduling. The firstsearch space may be a wireless device-specific search space. Theconfiguration parameters may comprise a parameter indicating enablingcross-carrier scheduling for the second search space. The wirelessdevice may determine that the second search space is for cross-carrierscheduling based on the parameter indicating enabling of cross-carrierscheduling. The configuration parameters may further indicate one ormore first DCI formats for the second search space. The wireless devicemay receive one or more second messages indicating one or more secondDCI formats for the third search space of the secondary cell. The one ormore second DCI formats may comprise the one or more first DCI formats.The wireless device may determine, based on the second search space, oneor more aggregation levels and one or more quantity of monitoringcandidates for an aggregation level. The wireless device may monitor,based on the one or more aggregation levels and the one or more quantityof monitoring candidates for the aggregation level, the third searchspace of the secondary cell. The primary cell may be one of: a primarycell of a master cell group; a primary cell of a secondary cell group;or a physical uplink control channel (PUCCH) cell of a PUCCH group. Thefirst search space may be a common search space or a wirelessdevice-specific search space, and the second search space may be awireless device-specific search space. The wireless device may compriseone or more processors; and memory storing instructions that, whenexecuted by the one or more processors, cause the wireless device toperform the described method, additional operations and/or include theadditional elements. A system may comprise the wireless deviceconfigured to perform the described method, additional operations and/orinclude the additional elements; and a base station configured to sendthe at least one resource assignment. A computer-readable medium maystore instructions that, when executed, cause performance of thedescribed method, additional operations and/or include the additionalelements.

A wireless device may perform a method comprising multiple operations.The wireless device may receive one or more messages comprisingconfiguration parameters for a primary cell. The configurationparameters may comprise: an indication of a secondary cell forcross-carrier scheduling the primary cell, wherein the primary cellcomprises a first search space and the secondary cell comprises a secondsearch space; parameters associated with the first search space; andparameters associated with the second search space. The wireless devicemay determine, based on the first search space of the primary cell, thesecond search space of the secondary cell. The wireless device maymonitor, based on the parameters associated with the first search spaceand the parameters associated with the second search space, the secondsearch space of the secondary cell for first downlink controlinformation (DCI). The wireless device may also perform one or moreadditional operations. The first DCI may comprise resource assignmentsfor the primary cell. The primary cell may further comprise a thirdsearch space. The configuration parameters may further comprise: anindication that cross-carrier scheduling is enabled for the first searchspace; and an indication that self-carrier scheduling is enabled for thethird search space. The monitoring the second search space may be basedon cross-carrier scheduling being enabled for the first search space.The wireless device may monitor, based on self-carrier scheduling beingenabled for the third search space, the third search space of theprimary cell for second DCI. The wireless device may receive a commandindicating activation of cross-carrier scheduling for the primary cell.The monitoring the second search space may be based on the activation ofcross-carrier scheduling for the primary cell. The parameters associatedwith the first search space may comprise an indication of a quantity ofcontrol channel candidates for the first search space. The parametersassociated with the second search space may comprise an indication ofmonitoring occasions for the second search space. The determining thesecond search space may comprises determining a search space indicatorof the second search space that is associated with a search spaceindicator of the first search space. The wireless device may compriseone or more processors; and memory storing instructions that, whenexecuted by the one or more processors, cause the wireless device toperform the described method, additional operations and/or include theadditional elements. A system may comprise the wireless deviceconfigured to perform the described method, additional operations and/orinclude the additional elements; and a base station configured to sendthe one or more messages. A computer-readable medium may storeinstructions that, when executed, cause performance of the describedmethod, additional operations and/or include the additional elements.

A wireless device may perform a method comprising multiple operations.The wireless device may receive one or more messages comprisingconfiguration parameters for a primary cell. The configurationparameters may comprise: a first indication indicating that a firstsearch space of the primary cell is enabled with cross-carrierscheduling; and a second indication, of a secondary cell, forcross-carrier scheduling the primary cell. The wireless device maydetermine, based on the first search space of the primary cell, a secondsearch space of the secondary cell. The wireless device may receive, viathe second search space of the secondary cell, at least one resourceassignment for the primary cell. The wireless device may also performone or more additional operations. The wireless device may receive acommand indicating activation of cross-carrier scheduling for theprimary cell. The receiving, via the second search space of thesecondary cell, the at least one resource assignment for the primarycell may be based on the activation of cross-carrier scheduling for theprimary cell. The wireless device may receive, via the primary cell andbased on the at least one resource assignment, downlink data. Thedetermining the second search space may comprise determining a searchspace indicator of the second search space that is the same as a searchspace indicator of the first search space. The determining the secondsearch space may comprise determining the second search space based onan association with the first search space. The wireless device maycomprise one or more processors; and memory storing instructions that,when executed by the one or more processors, cause the wireless deviceto perform the described method, additional operations and/or includethe additional elements. A system may comprise the wireless deviceconfigured to perform the described method, additional operations and/orinclude the additional elements; and a base station configured to sendthe one or more messages. A computer-readable medium may storeinstructions that, when executed, cause performance of the describedmethod, additional operations and/or include the additional elements.

A wireless device may perform a method comprising multiple operations.The wireless device may receive configuration parameters indicating: acell index of a secondary cell cross-carrier scheduling a primary cell;one or more wireless device-specific search spaces of a downlinkbandwidth part (DL BWP) of the primary cell; and one or more controlresource sets (CORESETs) of the DL BWP of the primary cell. The wirelessdevice may activate the DL BWP as an active DL BWP of the primary cell.The wireless device may determine self-carrier scheduling of the DL BWPbased on a wireless device-specific search space of the one or morewireless device-specific search spaces being associated with a CORESETof the one or more CORESETs. The wireless device may monitor, based onthe determining self-carrier scheduling of the DL BWP, the DL BWP fordownlink control information (DCI) indicating resources for the primarycell. The wireless device may also perform one or more additionaloperations. The DL BWP may be an initial DL BWP. The DL BWP may be adefault DL BWP. The wireless device may receive one or more messagesindicating second configuration parameters The second configurationparameters may indicate: one or more second wireless device-specificsearch spaces of a second DL BWP of the primary cell; and one or moresecond CORESETs of the second DL BWP of the primary cell. The wirelessdevice may receive a command indicating switching from the DL BWP to thesecond DL BWP of the primary cell. The wireless device may activate,based on the receiving the command, the second DL BWP as the active DLBWP of the primary cell. The command may be DCI comprising a BWP indexof the second DL BWP. The wireless device may determine cross-carrierscheduling of the second DL BWP based on none of CORESET indexes of theone or more second wireless device-specific search spaces being the sameas a CORESET index of a CORESET of the one or more second CORESETs. Thewireless device may monitor, based on the determining cross-carrierscheduling of the second DL BWP, the secondary cell for second DCIindicating resources for the primary cell. The second DL BWP may or maynot be an initial DL BWP or a default DL BWP. The wireless device mayactivate the DL BWP as an active DL BWP of the primary cell based ontriggering a random access procedure. The wireless device may activatethe DL BWP as an active DL BWP of the primary cell based on an expiry ofa BWP inactivity timer of the primary cell. The wireless device maycomprise one or more processors; and memory storing instructions that,when executed by the one or more processors, cause the wireless deviceto perform the described method, additional operations and/or includethe additional elements. A system may comprise the wireless deviceconfigured to perform the described method, additional operations and/orinclude the additional elements; and a base station configured to sendthe configuration parameters. A computer-readable medium may storeinstructions that, when executed, cause performance of the describedmethod, additional operations and/or include the additional elements.

A wireless device may perform a method comprising multiple operations.The wireless device may also perform one or more additional operations.The wireless device may comprise one or more processors; and memorystoring instructions that, when executed by the one or more processors,cause the wireless device to perform the described method, additionaloperations and/or include the additional elements. A system may comprisethe wireless device configured to perform the described method,additional operations and/or include the additional elements; and a basestation configured to send the DCI. A computer-readable medium may storeinstructions that, when executed, cause performance of the describedmethod, additional operations and/or include the additional elements.

A wireless device may perform a method comprising multiple operations.The wireless device may receive configuration parameters indicating: acell index of a secondary cell cross-carrier scheduling a primary cell;one or more wireless device-specific search spaces of a downlinkbandwidth part (DL BWP) of the primary cell; and one or more controlresource sets (CORESETs) of the DL BWP of the primary cell. The wirelessdevice may activate the DL BWP as an active DL BWP of the primary cell.The wireless device may determine cross-carrier scheduling of the DL BWPbased none of CORESET indexes of the one or more wirelessdevice-specific search spaces being the same as a CORESET index of aCORESET of the one or more CORESETs. The wireless device may monitor,based on the determining cross-carrier scheduling of the DL BWP, thesecondary cell for downlink control information (DCI) indicatingresources for the primary cell. The wireless device may also perform oneor more additional operations. The wireless device may comprise one ormore processors; and memory storing instructions that, when executed bythe one or more processors, cause the wireless device to perform thedescribed method, additional operations and/or include the additionalelements. A system may comprise the wireless device configured toperform the described method, additional operations and/or include theadditional elements; and a base station configured to send theconfiguration parameters. A computer-readable medium may storeinstructions that, when executed, cause performance of the describedmethod, additional operations and/or include the additional elements.

A wireless device may perform a method comprising multiple operations.The wireless device may receive one or more messages comprisingconfiguration parameters for a first cell. The configuration parametersmay comprise: a scheduling cell index of a second cell cross-carrierscheduling the first cell; an initial downlink bandwidth part (DL BWP)index of an initial DL BWP; and a first DL BWP index of a first DL BWPdifferent from the initial DL BWP. The wireless device may activate theinitial DL BWP of the first cell as an active DL BWP of the first cell.The wireless device may, based on the activating the initial DL BWP:determining self-carrier scheduling for the first cell; and monitor, oneor more first search spaces of the initial DL BWP of the first cell, forfirst downlink control information (DCI) indicating resources for thefirst cell. The wireless device may switch to the first DL BWP as theactive DL BWP of the first cell. The wireless device may, based on theswitching: enable cross-carrier scheduling for the first cell; andmonitor, one or more second search spaces of the second cell, for secondDCI indicating resources for the first cell. The wireless device mayalso perform one or more additional operations. The wireless device maycomprise one or more processors; and memory storing instructions that,when executed by the one or more processors, cause the wireless deviceto perform the described method, additional operations and/or includethe additional elements. A system may comprise the wireless deviceconfigured to perform the described method, additional operations and/orinclude the additional elements; and a base station configured to sendthe one or more messages. A computer-readable medium may storeinstructions that, when executed, cause performance of the describedmethod, additional operations and/or include the additional elements.

A wireless device may perform a method comprising multiple operations.The wireless device may receive one or more messages comprisingconfiguration parameters for a primary cell. The configurationparameters may indicate: a common search space of the primary cell;

a first wireless device-specific search space of the primary cell; and asecond wireless device-specific search space, of a secondary cell, forcross-carrier scheduling of the primary cell. The wireless device maymonitor, for first downlink control information (DCI) indicatingresources of the primary cell, the common search space of the primarycell. The wireless device may monitor, for second DCI indicatingresources of the primary cell, the first wireless device-specific searchspace of the primary cell. The wireless device may, based oncross-carrier scheduling of the primary cell: continue monitoring, forthe first DCI, the common search space of the primary cell; stopmonitoring, for the second DCI, the first wireless device-specificsearch space of the primary cell; and start monitoring, for third DCIindicating resources of the primary cell, the second wirelessdevice-specific search space of the secondary cell. The wireless devicemay also perform one or more additional operations. The wireless devicemay receive, via the second wireless device specific search space of thesecondary cell, DCI indicating first resources of the primary cell. Thewireless device may communicate, based on receiving the DCI indicatingfirst resources of the primary cell, via the first resources of theprimary cell. The wireless device may receive, via the common searchspace of the primary cell, DCI indicating first resources of the primarycell. The wireless device may communicate, based on receiving the DCIindicating first resources of the primary cell, via the first resourcesof the primary cell. The primary cell and the secondary cell may belongto a physical uplink control channel (PUCCH) group. The wireless devicemay transmit a hybrid automatic repeat request (HARQ) feedback via theprimary cell. The first DCIs may be based on one or more first DCIformats. The one or more first DCI formats may comprise a DCI format 1_0and a DCI format 0_0. The second DCIs may be based on one or more secondDCI formats. The third DCIs may be based on the one or more second DCIformats. The one or more second DCI formats may comprise a DCI format1_1 and a DCI format 0_1. The one or more second DCI formats maycomprise a DCI format 1_2 and a DCI format 0_2. The one or more secondDCI formats may comprise a DCI format 3_0 and a DCI format 3_1. Thefirst DCI may comprise cyclic redundancy check (CRC) bits scrambled withone of one or more first radio network temporary identifier (RNTIs). Thesecond DCI may comprises CRC bits scrambled with one of one or moresecond RNTIs. The third DCI may comprise CRC bits scrambled with the oneof one or more second RNTIs. The one or more first RNTIs may comprise acell-RNTI (C-RNTI), a system information-RNTI (SI-RNTI), and a randomaccess-RNTI (RA-RNTI). The one or more second RNTIs may comprise acell-RNTI (C-RNTI) and configured scheduling-RNTI (CS-RNTI). Thewireless device may receive one or more radio resource control (RRC)messages indicating a cell indicator of the secondary cell. The wirelessdevice may enable the cross-carrier scheduling of the primary cell basedon receiving at least one of: a radio resource control (RRC) message; amedium access control control element (MAC CE); or DCI. The wirelessdevice may start monitoring the second wireless device specific searchspace of the secondary cell based on enabling cross-carrier schedulingof the primary cell. The monitoring, for the first DCI, the commonsearch space may comprise monitoring, for the first DCI, based on a DCIformat 1_0 with a system information-radio network temporary identifier(SI-RNTI).

The monitoring, for the first DCIs, the common search space may comprisemonitoring, for the first DCI, based on a DCI format 1_0 with a randomaccess-radio network temporary identifier (RA-RNTI). The monitoring, forthe first DCI, the common search space may comprise monitoring, for thefirst DCI, based on a DCI format 1_0 with cell-radio network temporaryidentifier (C-RNTI). The wireless device may comprise one or moreprocessors; and memory storing instructions that, when executed by theone or more processors, cause the wireless device to perform thedescribed method, additional operations and/or include the additionalelements. A system may comprise the wireless device configured toperform the described method, additional operations and/or include theadditional elements; and a base station configured to send the one ormore messages. A computer-readable medium may store instructions that,when executed, cause performance of the described method, additionaloperations and/or include the additional elements.

A wireless device may perform a method comprising multiple operations.The wireless device may receive one or more first messages comprisingfirst configuration parameters for a primary cell The configurationparameters may indicate: a common search space of the primary cell; anda first wireless device-specific search space of the primary cell. Thewireless device may, based on the receiving the one or more firstmessages: monitor, for first downlink control information (DCI)indicating resources of the primary cell, the common search space of theprimary cell; and monitor, for second DCI indicating resources of theprimary cell, the first wireless device-specific search space of theprimary cell. The wireless device may receive one or more secondmessages indicating a second wireless device-specific search space, of asecondary cell, for cross-carrier scheduling of the primary cell. Thewireless device may, based on the receiving the one or more secondmessages: continue monitoring, for the first DCI, the common searchspace of the primary cell; and start monitoring, for third DCIindicating resources of the primary cell, the second wirelessdevice-specific search space of the secondary cell. The wireless devicemay also perform one or more additional operations. The wireless devicemay, based on receiving the one or more second messages, stopmonitoring, for the second DCI, the first wireless device-specificsearch space of the primary cell. The wireless device may receive, viathe second wireless device-specific search space of the secondary cell,DCI indicating first resources of the primary cell. The wireless devicemay communicate, based on the receiving the DCI indicating firstresources of the primary cell, via the first resources of the primarycell. The wireless device may receive, via the common search space ofthe primary cell, DCI indicating first resources of the primary cell.The wireless device may communicate, based on the receiving the DCIindicating first resources of the primary cell, via the first resourcesof the primary cell. The wireless device may enable cross-carrierscheduling of the primary cell based on receiving at least one of: theone or more second messages; a radio resource control (RRC) message; amedium access control control element (MAC CE); or DCI. The one or moresecond messages may indicate a cell indicator of the secondary cell. Thewireless device may comprise one or more processors; and memory storinginstructions that, when executed by the one or more processors, causethe wireless device to perform the described method, additionaloperations and/or include the additional elements. A system may comprisethe wireless device configured to perform the described method,additional operations and/or include the additional elements; and a basestation configured to send the one or more first messages. Acomputer-readable medium may store instructions that, when executed,cause performance of the described method, additional operations and/orinclude the additional elements.

A wireless device may perform a method comprising multiple operations.The wireless device may receive one or more messages comprisingconfiguration parameters for a primary cell. The configurationparameters may indicate: a common search space of the primary cell; anda wireless device-specific search space, of a secondary cell, forcross-carrier scheduling of the primary cell. The wireless device may,based on the receiving the one or more messages: monitor, based on afirst DCI format and for first downlink control information (DCI)indicating resources of the primary cell, the common search space of theprimary cell; and monitor, based on a second DCI format and for secondDCI indicating resources of the primary cell, the wirelessdevice-specific search space of the secondary cell. The second DCIformat may be different from the first DCI format. The wireless devicemay also perform one or more additional operations. The configurationparameters may further indicate a second wireless device-specific searchspace of the primary cell. The wireless device may receive a commandindicating deactivation of cross-carrier scheduling of the primary cell.The wireless device may, based on the receiving the command: stopmonitoring, for the second DCI, the wireless device-specific searchspace of the secondary cell; and start monitoring, for third DCI basedon the second DCI format, the second wireless device-specific searchspace of the primary cell. The wireless device may receive, via thewireless device-specific search space of the secondary cell, DCIindicating first resources of the primary cell. The wireless device maycommunicate, based on the receiving the DCI indicating first resourcesof the primary cell, via the first resources of the primary cell. Thewireless device may receive, via the common search space of the primarycell, DCI indicating first resources of the primary cell. The wirelessdevice may communicate, based on the receiving the DCI indicating firstresources of the primary cell, via the first resources of the primarycell. The wireless device may enable cross-carrier scheduling based onthe receiving the one or more first messages. The wireless device maymonitor the wireless device-specific search space of the secondary cellbased on the enabling cross-carrier scheduling of the primary cell. Thewireless device may comprise one or more processors; and memory storinginstructions that, when executed by the one or more processors, causethe wireless device to perform the described method, additionaloperations and/or include the additional elements. A system may comprisethe wireless device configured to perform the described method,additional operations and/or include the additional elements; and a basestation configured to send the one or more messages. A computer-readablemedium may store instructions that, when executed, cause performance ofthe described method, additional operations and/or include theadditional elements.

A base station may perform a method comprising multiple operations. Thebase station may determine configuration parameters for a first cell.The configuration parameters may indicate: that the first cell is aphysical uplink control channel (PUCCH) cell of a PUCCH cell group; oneor more secondary cells of the PUCCH cell group; and one or moreparameters for cross-carrier scheduling. The one or more parameters mayindicate that a second cell of the one or more secondary cells is ascheduling cell of the first cell. The base station may transmit, to awireless device, one or more radio resource control (RRC) messagesindicating the configuration parameters. The base station may, based onthe cross-carrier scheduling: transmit, via the first cell, first DCIindicating resource for the first cell; and transmit, via the secondcell, second DCI indicating resource for the first cell. The basestation may receive, via the first cell, a PUCCH transmission comprisingan uplink signal corresponding to the first DCI and the second DCI. Thebase station may also perform one or more additional operations. Thebase station may comprise one or more processors; and memory storinginstructions that, when executed by the one or more processors, causethe base station to perform the described method, additional operationsand/or include the additional elements. A system may comprise the basestation configured to perform the described method, additionaloperations and/or include the additional elements; and a wireless deviceconfigured to send the PUCCH transmission. A computer-readable mediummay store instructions that, when executed, cause performance of thedescribed method, additional operations and/or include the additionalelements.

A wireless device may perform a method comprising multiple operations.The wireless device may receive one or more messages comprisingconfiguration parameters for a first cell. The configuration parametersmay indicate: a first search space of the first cell for monitoring,based on a first DCI format, for first downlink control information(DCI); a second search space of a second cell for monitoring, based onthe first DCI format, for second DCI; and one or more parameters forcross-carrier scheduling, wherein the one or more parameters indicatethat the second cell is a scheduling cell of the first cell. Thewireless device may monitor, for the first DCI based on the first DCIformat and comprising resource assignments for the first cell, the firstcell. The wireless device may switch from self-carrier scheduling tocross-carrier scheduling. The wireless device may, based on theswitching to cross-carrier scheduling: stop monitoring the first cellfor the first DCI; and start monitoring, for the second DCI based on thefirst DCI format and comprising resource assignments for the first cell,the second cell. The wireless device may also perform one or moreadditional operations. The wireless device may comprise one or moreprocessors; and memory storing instructions that, when executed by theone or more processors, cause the wireless device to perform thedescribed method, additional operations and/or include the additionalelements. A system may comprise the wireless device configured toperform the described method, additional operations and/or include theadditional elements; and a base station configured to send the one ormore messages. A computer-readable medium may store instructions that,when executed, cause performance of the described method, additionaloperations and/or include the additional elements.

A wireless device may perform a method comprising multiple operations.The wireless device may receive one or more messages comprisingconfiguration parameters for a primary cell. The configurationparameters may indicate a first search space of the primary cell and asecond search space of a secondary cell. The wireless device may monitorthe first search space of the primary cell for first downlink controlinformation (DCI) comprising at least one first resource assignment forthe primary cell. The wireless device may receive a command indicatingactivation of cross-carrier scheduling of the primary cell via thesecondary cell. The wireless device may, based on the receiving thecommand, start monitoring the second search space of the secondary cellfor second DCI comprising at least one second resource assignment forthe primary cell. The wireless device may also perform one or moreadditional operations. The command may indicate activation of one ormore secondary cells, wherein the one or more secondary cells maycomprise the secondary cell. The configuration parameters may indicatethat the secondary cell is a scheduling cell of the primary cell. Thecommand may indicate the activation of cross-carrier scheduling byindicating an activation of the secondary cell. The wireless device mayreceive, via the second search space of the secondary cell, the secondDCI comprising the at least one second resource assignment for theprimary cell. The wireless device may receive, via the primary cell andbased on the at least one second resource assignment, downlink data. Thecommand may comprise at least one of DCI or a medium access control(MAC) control element (CE). The command may be a secondary cellactivation and deactivation medium access control (MAC) control element(CE) command indicating activation of the secondary cell. The secondarycell activation and deactivation MAC CE command may comprise a bit,corresponding to a cell index of the secondary cell, indicatingactivation of the secondary cell. The command may comprise one or morebits for activating one or more secondary cells, comprising thesecondary cell, and a bit indicating enabling cross-carrier schedulingof the primary cell. The configuration parameters may comprise one ormore parameters for cross-carrier scheduling, wherein the one or moreparameters may indicate that the secondary cell is a scheduling cell ofthe primary cell. The command may comprise one or more bits indicatingan activation of the secondary cell and a bit indicating enablingcross-carrier scheduling of the primary cell. The command may compriseone or more bits for activating one or more secondary cells, comprisingthe secondary cell, and a field indicating a cell index of the secondarycell. The wireless device may receive a second command indicating anactivation of a second secondary cell. The wireless device may monitorone or more search spaces of the second secondary cell for third DCIcomprising at least one third resource assignment for the primary cell.The wireless device may determine, based on the second command, that thesecond secondary cell is a scheduling cell of the primary cell. Thecommand may comprise one or more bits for activating one or moresecondary cells, comprising the secondary cell, a first field indicatingenabling cross-carrier scheduling of the primary cell, and a secondfield indicating a cell index of the secondary cell. The wireless devicemay, based on the receiving the command, stop monitoring the firstsearch space of the primary cell for the first DCI. The wireless devicemay receive a third command indicating deactivation of cross-carrierscheduling of the primary cell via the secondary cell. The third commandmay indicate deactivation of cross-carrier scheduling of the primarycell via the secondary cell by indicating deactivation of the secondarycell. The wireless device may, based on the receiving the third command,stop monitoring the second search space of the secondary cell. Thewireless device may, based on the third command: deactivatecross-carrier scheduling of the primary cell via the secondary cell;activate self-carrier scheduling of the primary cell; and monitor thefirst search space of the primary cell for the first DCI. The wirelessdevice may, based on receiving the command, determine a switchinglatency. The switching latency may comprise an activation latency of thesecondary cell and a delay offset. The starting monitoring the secondsearch space of the secondary cell for the second DCI may comprisestarting monitoring the second search space of the secondary cell basedon a switching latency following the receiving the command. The primarycell may be one of: a primary cell of a master cell group; a primarycell of a secondary cell group; or a physical uplink control channel(PUCCH) cell of a PUCCH group. The wireless device may comprise one ormore processors; and memory storing instructions that, when executed bythe one or more processors, cause the wireless device to perform thedescribed method, additional operations and/or include the additionalelements. A system may comprise the wireless device configured toperform the described method, additional operations and/or include theadditional elements; and a base station configured to send the command.A computer-readable medium may store instructions that, when executed,cause performance of the described method, additional operations and/orinclude the additional elements.

A wireless device may perform a method comprising multiple operations.The wireless device may monitor, based on a first downlink controlinformation (DCI) format, a first search space of a primary cell forfirst DCI comprising at least one first resource assignment for theprimary cell. The wireless device may receive a command indicatingactivation of cross-carrier scheduling of the primary cell by asecondary cell. The wireless device may, based on the receiving thecommand, start monitoring, based on a second DCI format, a second searchspace of the secondary cell for second DCI comprising at least onesecond resource assignment for the primary cell. The wireless device mayreceive, via the second search space of the secondary cell, the secondDCI comprising the at least one second resource assignment for theprimary cell. The wireless device may also perform one or moreadditional operations. The wireless device may receive one or moremessages comprising configuration parameters for the primary cell. Theconfiguration parameters may indicate the first search space of theprimary cell and the second search space of the secondary cell. Thecommand may comprise an indication of activation of the secondary cell.The wireless device may monitor, based on the second DCI format, a thirdsearch space of the primary cell for third DCI comprising at least onethird resource assignment for the primary cell. The wireless device may,based on receiving the command, stop monitoring the third search spaceof the primary cell for third DCI. The wireless device may receive, viathe primary cell and based on the at least one first resourceassignment, downlink data. The command may comprise at least one of DCIor a medium access control (MAC) control element (CE). The wirelessdevice may comprise one or more processors; and memory storinginstructions that, when executed by the one or more processors, causethe wireless device to perform the described method, additionaloperations and/or include the additional elements. A system may comprisethe wireless device configured to perform the described method,additional operations and/or include the additional elements; and a basestation configured to send the command. A computer-readable medium maystore instructions that, when executed, cause performance of thedescribed method, additional operations and/or include the additionalelements.

A wireless device may perform a method comprising multiple operations.The wireless device may monitor, based on a first radio network trafficidentifier (RNTI), a first search space of a primary cell for firstdownlink control information (DCI) comprising at least one firstresource assignment for the primary cell. The wireless device mayreceive a command indicating activation of cross-carrier scheduling ofthe primary cell by a secondary cell. The wireless device may, based onthe receiving the command, start monitoring, based on a second RNTI, asecond search space of the secondary cell for second DCI comprising atleast one second resource assignment for the primary cell. The wirelessdevice may also perform one or more additional operations. The wirelessdevice may receive one or more messages comprising configurationparameters for the primary cell. The configuration parameters mayindicate the first search space of the primary cell and the secondsearch space of the secondary cell. The command may comprise anindication of activation of the secondary cell. The monitoring the firstsearch space of the primary cell may comprise monitoring the firstsearch space of the primary cell based on a first DCI format. Themonitoring the second search space of secondary cell may comprisemonitoring the second search space of the secondary cell based on asecond DCI format. The wireless device may receive, via the secondsearch space of the secondary cell, the second DCI comprising the atleast one second resource assignment for the primary cell. The wirelessdevice may receive, via the primary cell and based on the at least onesecond resource assignment, downlink data. The command may comprise atleast one of DCI or a medium access control (MAC) control element (CE).The wireless device may comprise one or more processors; and memorystoring instructions that, when executed by the one or more processors,cause the wireless device to perform the described method, additionaloperations and/or include the additional elements. A system may comprisethe wireless device configured to perform the described method,additional operations and/or include the additional elements; and a basestation configured to send the command. A computer-readable medium maystore instructions that, when executed, cause performance of thedescribed method, additional operations and/or include the additionalelements.

A wireless device may perform a method comprising multiple operations.The wireless device may receive one or more messages comprisingconfiguration parameters for a first cell. The configuration parametersmay indicate: a first search space of the first cell; a second searchspace of the first cell; a third search space of a second cell; and oneor more parameters for cross-carrier scheduling. The one or moreparameters may indicate that the second cell is a scheduling cell of thefirst cell. The wireless device may monitor the first search space forfirst downlink control information (DCI) based on a first DCI format.The wireless device may monitor the second search space for second DCIbased on the second DCI format. The wireless device may receive acommand indicating switching from self-carrier scheduling tocross-carrier scheduling for the first cell. The wireless device may,based on receiving the command: continue monitoring the first searchspace for the first DCI based on the first DCI format; stop monitoringthe second search space for the second DCI based on the second DCIformat; and start monitoring the third search space for third DCI basedon the second DCI format. The wireless device may also perform one ormore additional operations. The command may be at least one of: a radioresource control (RRC) command; a medium access control (MAC) controlelement (CE); or DCI. The command may indicate an activation of thesecond cell. The first cell may be a primary cell of a cell group or aprimary cell of a physical uplink control channel (PUCCH) group. Thesecond cell may be a secondary cell. The wireless device may receive asecond command indicating switching from cross-carrier scheduling forthe first cell to self-carrier scheduling for the first cell. Thewireless device may, based on the receiving the second command, stopmonitoring the third search space for the third DCI. The wireless devicemay, based on the receiving the second command, start monitoring thesecond search space for the second DCI. The wireless device may, basedon the receiving the second command, continue monitoring the firstsearch space for the first DCI. The first DCI may be scheduling DCI fordownlink data or uplink data of the first cell. The first DCI may begroup common DCI comprising one or more of: slot formation information(SFI); pre-emption indication; or transmission power control (TPC)command for one or more uplink channels. The one or more uplink channelsmay be one or more of: a physical uplink control channel (PUCCH); aphysical uplink scheduled channel (PUSCH); or a sounding referencesignal (SRS) channel. The wireless device may comprise one or moreprocessors; and memory storing instructions that, when executed by theone or more processors, cause the wireless device to perform thedescribed method, additional operations and/or include the additionalelements. A system may comprise the wireless device configured toperform the described method, additional operations and/or include theadditional elements; and a base station configured to send the command.A computer-readable medium may store instructions that, when executed,cause performance of the described method, additional operations and/orinclude the additional elements.

A wireless device may perform a method comprising multiple operations.The wireless device may receive one or more messages comprisingconfiguration parameters for cross-carrier scheduling for a first cell.The wireless device may receive a command indicating that a second cellis a scheduling cell for the first cell. The wireless device mayreceive, via the second cell, downlink control information (DCI)comprising a resource assignment for the first cell. The wireless devicemay communicate, via the first cell and based on the resourceassignment, with a base station. The wireless device may also performone or more additional operations. The first cell may be a primary cellof a cell group or a physical uplink control channel (PUCCH) group. Thesecond cell may be a secondary cell of the cell group or a physicaluplink control channel (PUCCH) group. The command may comprise one ormore fields indicating an identifier of the second cell. Theconfiguration parameters may indicate the second cell. The command maybe a secondary cell activation/deactivation medium access control (MAC)control element (CE). The MAC CE may indicate an activation of thesecond cell, wherein the second cell may be configured as the schedulingcell for the first cell via radio resource control (RRC) signaling. TheMAC CE may comprise a bit field indicating activation of cross-carrierscheduling for the first cell. The wireless device may ignore the bitfield indicating activation of cross-carrier scheduling based on thecross-carrier scheduling being already activated. The wireless devicemay determine the second cell, wherein the second cell may have a lowestcell index among one or more secondary cells activated via the secondarycell activation/deactivation MAC CE. The MAC CE may comprise a bit fieldindicating a cell index of the second cell for cross-carrier schedulingof the first cell. The wireless device may activate, based on receivingthe command, the second cell. The wireless device may activatecross-carrier scheduling for the first cell based on the activation ofthe second cell. The wireless device may activate cross-carrierscheduling for the first cell via the second cell. The wireless devicemay comprise one or more processors; and memory storing instructionsthat, when executed by the one or more processors, cause the wirelessdevice to perform the described method, additional operations and/orinclude the additional elements. A system may comprise the wirelessdevice configured to perform the described method, additional operationsand/or include the additional elements; and a base station configured tosend the command. A computer-readable medium may store instructionsthat, when executed, cause performance of the described method,additional operations and/or include the additional elements.

A wireless device may perform a method comprising multiple operations.The wireless device may receive one or more messages comprisingconfiguration parameters for a first cell. The configuration parametersmay comprise: an indication of cross-carrier scheduling for the firstcell; an indication of one or more first downlink control information(DCI) formats for self-carrier scheduling; an indication of one or moresecond DCI formats for cross-carrier scheduling; and an indication ofone or more first search spaces for monitoring for first DCIs comprisingresource assignments for the first cell. The wireless device may receivea command indicating that a second cell is a scheduling cell for thefirst cell. The wireless device may determine one or more second searchspaces of the second cell based on the one or more second DCI formatsfor cross-carrier scheduling. The wireless device may monitor, based onthe one or more first DCI formats and for the first DCIs comprisingresource assignments for the first cell, the one or more first searchspaces of the first cell. The wireless device may monitor, based on theone or more second DCI formats and for second DCIs comprising resourceassignments for the first cell, the one or more second search spaces ofthe second cell. The wireless device may also perform one or moreadditional operations. The wireless device may monitor for the firstDCIs based on a first radio network traffic identifier (RNTI). Thewireless device may monitor for the second DCIs based on a second radionetwork traffic identifier (RNTI). The wireless device may determine afirst DCI size of the one or more second DCI formats based on at leastone of an active downlink bandwidth part (BWP) or an active uplink BWPof the second cell. The wireless device may align a second DCI size,based on an active downlink BWP or an active uplink BWP of the firstcell, of the one or more second DCI formats to the first DCI size. Theone or more first search spaces may be cell-specific search spacesand/or wireless device-specific search spaces. The one or more first DCIformats may be fallback DCI formats such as DCI format 1_0 and DCIformat 0_0. The one or more second search spaces may be wirelessdevice-specific search spaces. The one or more second DCI formats may benon-fallback DCI formats such as DCI format 1_1 and DCI format 0_1. Thewireless device may comprise one or more processors; and memory storinginstructions that, when executed by the one or more processors, causethe wireless device to perform the described method, additionaloperations and/or include the additional elements. A system may comprisethe wireless device configured to perform the described method,additional operations and/or include the additional elements; and a basestation configured to send the command. A computer-readable medium maystore instructions that, when executed, cause performance of thedescribed method, additional operations and/or include the additionalelements.

A wireless device may perform a method comprising multiple operations.The wireless device may receive one or more radio resource control (RRC)messages comprising configuration parameters for a first cell. Theconfiguration parameters may indicate: one or more monitoring occasionsof a first search space of the first cell; and a second search space ofa second cell for cross-carrier scheduling of the first cell. The secondcell may be cross-carrier scheduling the first cell. The wireless devicemay receive group-common downlink control information (GC-DCI)comprising a slot format indication (SFI) of one or more slots for thefirst cell. The wireless device may, based on the GC-DCI, determine thata first monitoring occasion of the one or more monitoring occasions ofthe first search space fully overlaps with a downlink resource of afirst slot of the first cell. The wireless device may, based on thefirst monitoring occasion being overlapped with the downlink resource,monitor, the first monitoring occasion, for first downlink controlinformation (DCI) comprising resource assignment for the first cell. Thewireless device may determine that a second monitoring occasion of theone or more monitoring occasions of the first search space does notfully overlap with a downlink resource of a second slot of the firstcell. The wireless device may, based on the second monitoring occasionnot being overlapped with the downlink resource, monitor, a monitoringoccasion of the second search space during the second slot, for secondDCI comprising resource assignments for the first cell. The wirelessdevice may also perform one or more additional operations. The wirelessdevice may comprise one or more processors; and memory storinginstructions that, when executed by the one or more processors, causethe wireless device to perform the described method, additionaloperations and/or include the additional elements. A system may comprisethe wireless device configured to perform the described method,additional operations and/or include the additional elements; and a basestation configured to send the GC-DCI. A computer-readable medium maystore instructions that, when executed, cause performance of thedescribed method, additional operations and/or include the additionalelements.

A wireless device may perform a method comprising multiple operations.The wireless device may receive one or more messages comprisingconfiguration parameters for a first cell. The configuration parametersmay comprise: a scheduling cell index of a scheduling cell; one or morefirst parameters for a first search space of the first cell formonitoring for first downlink control information (DCI) schedulingresource assignments of data for the first cell; and one or more secondparameters for a second search space of the first cell for monitoringfor second DCI scheduling resource assignments of data for the firstcell. The one or more second parameters may comprise: a second searchspace index of the second search space; and an indication ofcross-carrier scheduling. The wireless device may monitor the firstsearch space of the first cell and the second search space of the firstcell. The wireless device may receive a command indicating an activationof cross-carrier scheduling for the first cell. The wireless device may,based on the receiving the command: determine a third search space ofthe scheduling cell based on the one or more second parameters for thesecond search space of the first cell; continue monitoring the firstsearch space of the first cell for the one or more first DCIs; stopmonitoring the second search space of the first cell; and monitor thethird search space of the scheduling cell for the one or more secondDCIs. The wireless device may also perform one or more additionaloperations. The wireless device may comprise one or more processors; andmemory storing instructions that, when executed by the one or moreprocessors, cause the wireless device to perform the described method,additional operations and/or include the additional elements. A systemmay comprise the wireless device configured to perform the describedmethod, additional operations and/or include the additional elements;and a base station configured to send the command. A computer-readablemedium may store instructions that, when executed, cause performance ofthe described method, additional operations and/or include theadditional elements.

One or more of the operations described herein may be conditional. Forexample, one or more operations may be performed if certain criteria aremet, such as in a wireless device, a base station, a radio environment,a network, a combination of the above, and/or the like. Example criteriamay be based on one or more conditions such as wireless device and/ornetwork node configurations, traffic load, initial system set up, packetsizes, traffic characteristics, a combination of the above, and/or thelike. If the one or more criteria are met, various examples may be used.It may be possible to implement any portion of the examples describedherein in any order and based on any condition.

A base station may communicate with one or more of wireless devices.Wireless devices and/or base stations may support multiple technologies,and/or multiple releases of the same technology. Wireless devices mayhave some specific capability(ies) depending on wireless device categoryand/or capability(ies). A base station may comprise multiple sectors,cells, and/or portions of transmission entities. A base stationcommunicating with a plurality of wireless devices may refer to a basestation communicating with a subset of the total wireless devices in acoverage area. Wireless devices referred to herein may correspond to aplurality of wireless devices compatible with a given LTE, 5G, or other3GPP or non-3GPP release with a given capability and in a given sectorof a base station. A plurality of wireless devices may refer to aselected plurality of wireless devices, a subset of total wirelessdevices in a coverage area, and/or any group of wireless devices. Suchdevices may operate, function, and/or perform based on or according todrawings and/or descriptions herein, and/or the like. There may be aplurality of base stations and/or a plurality of wireless devices in acoverage area that may not comply with the disclosed methods, forexample, because those wireless devices and/or base stations may performbased on older releases of LTE, 5G, or other 3GPP or non-3GPPtechnology.

One or more parameters, fields, and/or information elements (IEs), maycomprise one or more information objects, values, and/or any otherinformation. An information object may comprise one or more otherobjects. At least some (or all) parameters, fields, IEs, and/or the likemay be used and can be interchangeable depending on the context. If ameaning or definition is given, such meaning or definition controls.

One or more elements in examples described herein may be implemented asmodules. A module may be an element that performs a defined functionand/or that has a defined interface to other elements. The modules maybe implemented in hardware, software in combination with hardware,firmware, wetware (e.g., hardware with a biological element) or acombination thereof, all of which may be behaviorally equivalent. Forexample, modules may be implemented as a software routine written in acomputer language configured to be executed by a hardware machine (suchas C, C++, Fortran, Java, Basic, Matlab or the like) or amodeling/simulation program such as Simulink, Stateflow, GNU Octave, orLabVIEWMathScript. Additionally or alternatively, it may be possible toimplement modules using physical hardware that incorporates discrete orprogrammable analog, digital and/or quantum hardware. Examples ofprogrammable hardware may comprise: computers, microcontrollers,microprocessors, application-specific integrated circuits (ASICs); fieldprogrammable gate arrays (FPGAs); and/or complex programmable logicdevices (CPLDs). Computers, microcontrollers and/or microprocessors maybe programmed using languages such as assembly, C, C++ or the like.FPGAs, ASICs and CPLDs are often programmed using hardware descriptionlanguages (HDL), such as VHSIC hardware description language (VHDL) orVerilog, which may configure connections between internal hardwaremodules with lesser functionality on a programmable device. Theabove-mentioned technologies may be used in combination to achieve theresult of a functional module.

One or more features described herein may be implemented in acomputer-usable data and/or computer-executable instructions, such as inone or more program modules, executed by one or more computers or otherdevices. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other data processing device. The computer executableinstructions may be stored on one or more computer readable media suchas a hard disk, optical disk, removable storage media, solid statememory, RAM, etc. The functionality of the program modules may becombined or distributed as desired. The functionality may be implementedin whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike. Particular data structures may be used to more effectivelyimplement one or more features described herein, and such datastructures are contemplated within the scope of computer executableinstructions and computer-usable data described herein.

A non-transitory tangible computer readable media may compriseinstructions executable by one or more processors configured to causeoperations of multi-carrier communications described herein. An articleof manufacture may comprise a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g., a wirelessdevice, wireless communicator, a wireless device, a base station, andthe like) to allow operation of multi-carrier communications describedherein. The device, or one or more devices such as in a system, mayinclude one or more processors, memory, interfaces, and/or the like.Other examples may comprise communication networks comprising devicessuch as base stations, wireless devices or user equipment (wirelessdevice), servers, switches, antennas, and/or the like. A network maycomprise any wireless technology, including but not limited to,cellular, wireless, WiFi, 4G, 5G, any generation of 3GPP or othercellular standard or recommendation, any non-3GPP network, wirelesslocal area networks, wireless personal area networks, wireless ad hocnetworks, wireless metropolitan area networks, wireless wide areanetworks, global area networks, satellite networks, space networks, andany other network using wireless communications. Any device (e.g., awireless device, a base station, or any other device) or combination ofdevices may be used to perform any combination of one or more of stepsdescribed herein, including, for example, any complementary step orsteps of one or more of the above steps.

Although examples are described above, features and/or steps of thoseexamples may be combined, divided, omitted, rearranged, revised, and/oraugmented in any desired manner. Various alterations, modifications, andimprovements will readily occur to those skilled in the art. Suchalterations, modifications, and improvements are intended to be part ofthis description, though not expressly stated herein, and are intendedto be within the spirit and scope of the descriptions herein.Accordingly, the foregoing description is by way of example only, and isnot limiting.

The invention claimed is:
 1. A method comprising: monitoring, by a wireless device, for first downlink control information (DCI) indicating resources of a primary cell, a common search space of the primary cell; monitoring, for second DCI indicating resources of the primary cell, a first wireless device-specific search space of the primary cell; and based on cross-carrier scheduling of the primary cell: continuing monitoring, for the first DCI, the common search space of the primary cell; stopping monitoring, for the second DCI, the first wireless device-specific search space of the primary cell; and starting monitoring, for third DCI indicating resources of the primary cell, a second wireless device-specific search space of a secondary cell.
 2. The method of claim 1, further comprising, receiving one or more messages comprising configuration parameters for the primary cell, wherein the configuration parameters indicate: the common search space of the primary cell; the first wireless device-specific search space of the primary cell; and the second wireless device-specific search space, of the secondary cell, for cross-carrier scheduling of the primary cell.
 3. The method of claim 1, further comprising: receiving, via the second wireless device-specific search space of the secondary cell, DCI indicating first resources of the primary cell; and communicating, based on the receiving the DCI indicating first resources of the primary cell, via the first resources of the primary cell.
 4. The method of claim 1, further comprising: receiving, via the common search space of the primary cell, DCI indicating first resources of the primary cell; and communicating, based on the receiving the DCI indicating first resources of the primary cell, via the first resources of the primary cell.
 5. The method of claim 1, wherein: the first DCI is based on one or more first DCI formats; the second DCI is based on one or more second DCI formats; and the third DCI is based on the one or more second DCI formats.
 6. The method of claim 1, further comprising receiving one or more radio resource control (RRC) messages indicating a cell indicator of the secondary cell.
 7. The method of claim 1, further comprising enabling cross-carrier scheduling of the primary cell based on receiving at least one of: a radio resource control (RRC) message; a medium access control control element (MAC CE); or DCI.
 8. The method of claim 1, wherein the starting monitoring the second wireless device-specific search space of the secondary cell comprises starting monitoring the second wireless device-specific search space of the secondary cell based on enabling cross-carrier scheduling of the primary cell.
 9. The method of claim 1, wherein: the first DCI comprises cyclic redundancy check (CRC) bits scrambled with one of one or more first radio network temporary identifier (RNTIs); the second DCI comprises CRC bits scrambled with one of one or more second RNTIs; and the third DCI comprises CRC bits scrambled with the one of one or more second RNTIs.
 10. A method comprising: receiving, by a wireless device, one or more first message comprising configuration parameters for a primary cell, wherein the configuration parameters indicate: a common search space of the primary cell; and a first wireless device-specific search space of the primary cell; based on the receiving the one or more first messages: monitoring, for first downlink control information (DCI) indicating resources of the primary cell, the common search space of the primary cell; and monitoring, for second DCI indicating resources of the primary cell, the first wireless device-specific search space of the primary cell; receiving one or more second messages indicating a second wireless device-specific search space, of a secondary cell, for cross-carrier scheduling of the primary cell; and based on the receiving the one or more second messages: continuing monitoring, for the first DCI, the common search space of the primary cell; and starting monitoring, for third DCI indicating resources of the primary cell, the second wireless device-specific search space of the secondary cell.
 11. The method of claim 10, further comprising, based on receiving the one or more second messages, stopping monitoring, for the second DCI, the first wireless device-specific search space of the primary cell.
 12. The method of claim 10, further comprising: receiving, via the second wireless device-specific search space of the secondary cell, DCI indicating first resources of the primary cell; and communicating, based on the receiving the DCI indicating first resources of the primary cell, via the first resources of the primary cell.
 13. The method of claim 10, further comprising: receiving, via the common search space of the primary cell, DCI indicating first resources of the primary cell; and communicating, based on the receiving the DCI indicating first resources of the primary cell, via the first resources of the primary cell.
 14. The method of claim 10, further comprising enabling cross-carrier scheduling of the primary cell based on receiving at least one of: the one or more second messages; a radio resource control (RRC) message; a medium access control control element (MAC CE); or DCI.
 15. The method of claim 10, wherein the one or more second messages indicate a cell indicator of the secondary cell.
 16. A method comprising: receiving, by a wireless device, one or more messages comprising configuration parameters for a primary cell, wherein the configuration parameters indicate: a common search space of the primary cell; and a wireless device-specific search space, of a secondary cell, for cross-carrier scheduling of the primary cell; and based on the receiving the one or more messages: monitoring, based on a first DCI format and for first downlink control information (DCI) indicating resources of the primary cell, the common search space of the primary cell; and monitoring, based on a second DCI format and for second DCI indicating resources of the primary cell, the wireless device-specific search space of the secondary cell, wherein the second DCI format is different from the first DCI format.
 17. The method of claim 16, wherein the configuration parameters further indicate a second wireless device-specific search space of the primary cell, and wherein the method further comprises: receiving a command indicating deactivation of cross-carrier scheduling of the primary cell; and based on the receiving the command: stopping monitoring, for the second DCI, the wireless device-specific search space of the secondary cell; and starting monitoring, for third DCI based on the second DCI format, the second wireless device-specific search space of the primary cell.
 18. The method of claim 16, further comprising: receiving, via the wireless device-specific search space of the secondary cell, DCI indicating first resources of the primary cell; and communicating, based on the receiving the DCI indicating the first resources of the primary cell, via the first resources of the primary cell.
 19. The method of claim 16, further comprising: receiving, via the common search space of the primary cell, DCI indicating first resources of the primary cell; and communicating, based on the receiving the DCI indicating first resources of the primary cell, via the first resources of the primary cell.
 20. The method of claim 16, further comprising enabling cross-carrier scheduling of the primary cell based on the receiving the one or more messages, wherein the monitoring the wireless device-specific search space of the secondary cell comprises monitoring the wireless device-specific search space of the secondary cell based on the enabling cross-carrier scheduling of the primary cell. 